Airplane lands with vehicles on runway Narrowly avoids collision

Advertisement

The Aircraft Had Already Landed Before the Hazard Became Visible

Jazz Aviation flight QK-8319 was approaching Sault Ste. Marie's runway 30 on January 6, 2017. The Dash 8-300, registration C-FRUZ, carried 35 people.

Accident Facts

Date
6 January 2017
Aircraft
Jazz Aviation Dash 8-300 C-FRUZ
Location
Sault Ste. Marie, Ontario
Timeline
6 January 2017 —
QK-8319 operated from Toronto toward Sault Ste. Marie.
1.
Approach —
The Dash 8 approached runway 30.
2.
Communication problem —
The No. 2 radio was not transmitting or receiving.
3.
Landing —
The crew continued the approach and touched down.
4.
Rollout —
The crew saw a snowplow occupying the runway near the end.
5.
Resolution —
The aircraft stopped before reaching the vehicle.
6.

The crew used the aircraft's No. 2 radio to transmit their intentions on the mandatory frequency. Unknown to them, that radio was not transmitting or receiving.

The airplane continued the approach and landed. Only during the rollout did the crew see a snowplow on the runway near the far end. They were able to stop before reaching the vehicle.

The Radio Failure Removed the Warning Layer

That is a classic example of a system appearing normal from the cockpit while being ineffective from the outside. A pilot can make a radio call and hear silence without necessarily realizing that the radio has failed to transmit or receive.

The result was that the runway-occupancy information never reached the crew through the normal communication path.

The Snowplow Was a Runway-Occupancy Hazard

The incident is particularly serious because the Dash 8 was not merely taxiing toward a vehicle. It landed on the same runway and only recognized the snowplow during the rollout.

The available sources indicate that the crew was able to stop before contact. No collision occurred and no injuries were reported. That successful stop is the reason this remains a near-miss rather than an accident.

Runway safety depends on several layers working together: airport vehicles must know when they may enter a runway, aircraft must be able to communicate and receive traffic information and controllers or mandatory-frequency users must be able to identify conflicts.

In this case, the failed radio weakened one of those layers. The aircraft then reached the runway without receiving the warning that a functioning communication channel might have provided.

The Radio Failure Was Not Obvious From the Cockpit

That meant the crew could not assume that silence from other traffic or the airport meant the runway was clear. A mandatory frequency is useful only if the radio is actually functioning.

The snowplow was therefore able to remain outside the crew's awareness until visual detection during the rollout.

Why the Radio Failure Could Defeat a Mandatory-Frequency System

A mandatory frequency is only useful if the aircraft can transmit and receive on it. The C-FRUZ crew used the radio as intended, but the technical failure meant the runway-occupancy information was not reaching them.

Conclusion

QK-8319's landing ended safely because the crew saw the snowplow before reaching it. But the fact that they only saw it during rollout makes the event a serious runway-incursion warning.

The failed No. 2 radio prevented the normal communication layer from working. The aircraft still stopped in time, but the system had already allowed an occupied runway to appear clear to the arriving crew.

Sources

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

The weekly incident