Fatal Crash: Pilot Errors and Airline Safety Failures

Advertisement

Flight context

Crossair Flight 3597 was approaching Zurich late on the evening of 24 November 2001 when an apparently routine arrival became a controlled flight into terrain. The Avro 146-RJ100 was not suffering from an engine failure or a catastrophic structural defect. The accident developed because the aircraft was flown below the safe approach path while the crew was attempting to establish the runway environment in poor visibility.

The investigation became especially consequential because it did not stop at the cockpit. The captain had a documented history of navigation and procedural problems, while Crossair's management had continued to employ him in passenger operations. The accident therefore exposed two connected layers of risk: what happened on the flight and what the operator had done—or failed to do—before the flight ever departed.

Timeline
21:03:00 UTC —
HB-IXM established contact with Zurich Aerodrome Control (Tower).
1.
21:05–21:06 UTC —
The aircraft continued the VOR/DME approach toward Runway 28.
2.
21:06:10 UTC —
The crew was at the minimum descent altitude and continued descending.
3.
21:06:25 UTC —
The commander reported seeing the runway area.
4.
21:06:34 UTC —
The crew called for a go-around.
5.
21:06:36 UTC —
HB-IXM struck terrain short of Runway 28.
6.

The critical sequence

The immediate flight-path failure was straightforward: the aircraft was too low and too far from the runway. The crew had not maintained the required vertical and lateral position and did not recognize the terrain threat early enough to recover.

But the Swiss investigation identified a wider set of defenses that had already been weakened. The captain had previously demonstrated navigation and procedural deficiencies. He had failed attempts to upgrade to the MD-83, had been involved in earlier operational incidents, and had previously been removed from flight-instructor duties. Those events should have been signals to the operator about his suitability for increasingly demanding line operations.

Crossair's organizational response became part of the safety story. The company continued to use the captain for passenger flights despite his history. The investigation therefore showed how an individual's weaknesses can become an organizational risk when training, checking and management oversight do not close the loop.

Environmental and procedural defenses were also imperfect. The hills involved in the crash were not marked on the Jeppesen approach chart used by the crew, Zurich Runway 28 did not have a Minimum Safe Altitude Warning system, and the available visibility information was not adequate for the conditions. These factors did not replace the crew's responsibility to maintain terrain clearance, but they reduced the number of remaining barriers.

ATC decisions during the event

The approach was conducted in an environment where ATC could provide clearances and traffic information but could not see the aircraft's actual terrain-clearance margin. A controller may issue an approach clearance while the crew still has to determine whether the published minima, visual references and aircraft position make the approach safe. The investigation also examined the experience level of the controller working the tower and whether an alternative runway might have been offered earlier in the deteriorating weather. The key lesson is that ATC is a safety layer, not a substitute for approach monitoring inside the cockpit.

Investigation and aftermath

The official report classified the event as controlled flight into terrain. The investigation reconstructed the aircraft's navigation, approach profile, crew actions, airport equipment and operator history. It concluded that the accident was caused primarily by the crew's failure to follow the correct approach procedure and maintain terrain clearance, with additional safety deficiencies involving the charting, airport warning system, visibility determination and operator oversight.

What the record establishes

The strongest evidence in the Crossair investigation is the combination of the CVR, radar track and approach data. HB-IXM contacted Zurich Tower at 21:03 UTC, descended through the published approach profile, and continued below the minimum descent altitude before the crew recognized the terrain and attempted a go-around. The investigation examined the aircraft's navigation and flight-guidance systems and found no pre-existing technical defect that explains the loss of terrain clearance. The final sequence therefore rests on the crew's approach decisions, the visual references available at night, and the ATC environment rather than an unexplained aircraft failure.

What the sequence shows

Crossair 3597 matters because it demonstrates why accident investigation cannot end with the phrase 'pilot error.' The final control inputs occurred in the cockpit, but the conditions that allowed those errors to remain operationally acceptable had been developing for years. A robust safety system is supposed to identify recurring performance problems, correct them and prevent a pilot who is not adequately prepared for a task from reaching a situation in which the consequences become irreversible.

  • Maintain the published approach and terrain-clearance requirements.
  • Do not allow repeated training or checking concerns to become normalized.
  • Treat operator oversight as an active safety barrier, not paperwork.
  • Question whether airport equipment and approach design provide adequate protection in the actual weather.
  • Recognize CFIT risk before visual references disappear.

Accident facts

Date
24 November 2001
Aircraft
Avro 146-RJ100
Registration
HB-IXM
Flight
Crossair CRX3597
Route
Berlin Tegel → Zurich
Location
Bassersdorf, Switzerland
Outcome
24 fatalities; 9 survivors
Defining event
Controlled flight into terrain
Investigation
Swiss Aircraft Accident Investigation Bureau Final Report No. 1793

Sources

Sources
Primary investigation: Swiss Aircraft Accident Investigation Bureau Final Report No. 1793. Supporting sources: Aviation Safety Network or equivalent accident database for cross-reference; ATC/radar or docket material where released; contemporary newspaper/aviation reporting for context only. Primary-source facts and official probable-cause wording take precedence over secondary reporting.
Advertisement

Official Investigation Source

The weekly incident