Two Runways, Two Questions: Air Canada’s Grass Excursion and Greece’s F-16 Belly Landing
Two aviation incidents — one civilian in Montreal and one military in Zakynthos — ended without reported fatalities. The real story is not panic, but what these near-misses reveal about aviation safety under pressure.
Two aviation incidents in a single news cycle have produced the kind of images that make social media move faster than investigators: an Air Canada aircraft leaving the paved surface after landing in Montreal, and a Greek Air Force F-16C Fighting Falcon crash-landing at Zakynthos after a landing-gear malfunction.
The first case appears, at least from early reports, to be more alarming visually than catastrophic operationally. Air Canada flight AC774, arriving from Los Angeles, landed at Montréal–Trudeau Airport and then travelled into the grass while exiting the main runway. Passengers and crew were taken to the terminal, and no injuries were reported. The cause remains under investigation, which matters: a runway excursion after landing can involve anything from steering, braking, pavement condition, pilot input, mechanical issues, wind, taxiway geometry or communication timing.
The second incident was more dramatic. A Hellenic Air Force F-16C reportedly suffered a technical or landing gear-related malfunction during a training flight and made an emergency landing at Zakynthos International Airport. Images and early reporting suggest a belly landing or gear-related crash landing followed by fire, but the pilot survived and was reported to be in good condition. That outcome is not luck alone. It reflects ejection and emergency-training culture, airport emergency readiness, and the fact that military pilots prepare for scenarios that commercial passengers never want to imagine.
The temptation online is to connect these events into a single narrative of “aviation falling apart.” That may be emotionally satisfying, but it is not yet evidence. Aviation systems produce visible failures because they are under constant observation. One aircraft in the grass and one fighter jet on fire do not prove a systemic collapse. They do, however, raise a useful question: are airports, airlines and air forces operating with enough margin as schedules tighten, weather becomes more volatile and military training tempo rises?
Civilian aviation has learned to survive by making every incident a data point. The aviation industry does not need to wait for fatalities to ask what went wrong. Runway excursions are studied because they are warning signals: Was the aircraft stable? Was the runway contaminated? Did the crew follow normal rollout procedures? Were airport markings, runway exits or ground-control instructions clear? Air Canada will have to answer those questions, and passengers deserve a transparent report rather than a vague “under investigation” ending.
Military aviation faces a different but related problem. Fighter jets are high-performance machines that operate under stress. Mechanical faults, landing gear failures and training accidents are part of the risk environment. But when a NATO-aligned air force suffers a dramatic crash landing at a civilian airport, the incident also becomes political: are aircraft aging? Are maintenance budgets keeping pace? Are pilots training enough, or too much? Are civilian airports prepared for military emergencies?
Both incidents ended with the most important detail: no mass casualty outcome. That should not make them disappear from public attention. The correct response is neither panic nor dismissal. The right question is whether these events become lessons before the next one becomes worse.
The headline says planes ran into trouble. The deeper story is about resilience. Modern aviation is not safe because nothing goes wrong. It is safe because things go wrong and the system is supposed to absorb them before lives are lost. Did it work this time? Mostly yes. Will investigators tell the public enough to trust that it will work next time?