LIVE · BRIEFING WIRE
FlightLogic Brief Daily aviation wire
← YouTube
● YT VIDEO ·Mentour Pilot ·August 1, 2026 ·15:00Z

This One Was UNACCEPTABLE!! | The Infuriating Story Of Bordeaux

Imagine sitting in the cockpit of a small single engine aircraft on a lovely Saturday morning just waiting for your takeoff clearance at the runway threshold. Sounds quite lovely, doesn't it? Well, it was lovely for this father and his son until an almost
Detailed analysis

The incident under examination took place at Bordeaux-Mérignac Airport (LFBD) on the morning of December 31st, when a nearly fully loaded Airbus A320 conducted its takeoff roll while a father-and-son crew in a light single-engine aircraft was positioned at the runway threshold awaiting clearance. While the full sequence of events and the eventual resolution require further detail, the setup described paints a picture of an airport whose operational complexity is easy to underestimate: two crossing runways (05/23 at 3,100m and 11/29 at 2,415m), scheduled airline traffic from carriers like easyJet, Volotea, and Transavia, a significant general aviation and flight training presence, and periodic military/test flight activity tied to Dassault's nearby facility, which regularly sends Rafale fighters and Falcon business jets through the same airspace. This is a textbook example of a mixed-traffic aerodrome, where fast jets, turboprops, gliders, and piston singles all compete for the same runway real estate under a bilingual (French/English) ATC environment.

For working pilots, the critical lesson embedded in this setup is the fragility of combined ATC positions during a period of what should have been low-to-moderate traffic. On the morning in question, Bordeaux tower was operating with only three controllers, with a single individual simultaneously working tower, ground, approach, and information duties — effectively the entire operation collapsed into one person, backed by an assistant and a supervisor. This is a legally and procedurally accepted practice at many airports worldwide during quieter periods, and in isolation it is not inherently unsafe. But the article rightly frames the central operational hazard: workload-based staffing decisions are inherently subjective, and gradual increases in controller task saturation are notoriously difficult to detect in real time, especially when the traffic mix — rather than raw volume — is what drives complexity. A tower controller juggling an A320 on an ILS approach, a light aircraft holding short for departure, and potentially a military or business jet transiting the area is dealing with wildly different closure rates, communication protocols, and situational pictures almost simultaneously. This is precisely the kind of environment where a single missed strip, misheard readback, or momentary lapse in scanning the runway can cascade into a serious loss of separation or, as apparently happened here, a conflict between a departing airliner and an aircraft still occupying the runway environment.

This event resonates well beyond Bordeaux because runway incursions remain one of the most persistent and stubborn safety threats in global aviation, consistently appearing near the top of ICAO, EASA, and FAA risk registers despite decades of technological mitigation (ASDE-X, runway status lights, EFVS, TCAS/RAAS alerting). Mixed-use regional airports — common throughout Europe, where point-to-point routing reduces reliance on mega-hubs — present a uniquely challenging environment because they combine high-performance jet operations with general aviation training traffic and irregular military/test flying, often under reduced staffing during "quiet" periods that are, in practice, anything but simple. For airline and business jet crews, the takeaway is a reinforcement of basic but essential discipline: maintaining a sterile cockpit and active visual scan during takeoff roll, cross-checking runway occupancy independently of ATC clearance whenever possible, and treating any ambiguity in a takeoff clearance — especially at unfamiliar or mixed-traffic fields — as grounds for a query rather than an assumption. For Part 91 and flight training operators flying light singles into busier controlled fields, it underscores the danger of complacency when holding short or lined up at a threshold, particularly at airports where controller attention is known to be divided across multiple functions.

More broadly, this incident feeds into an ongoing industry conversation about controller staffing models, fatigue, and the limits of "combined position" operations at medium-sized international airports that nonetheless carry hub-like complexity. As European air traffic continues to recover and grow post-pandemic, and as secondary airports increasingly absorb both low-cost carrier growth and general aviation activity, the staffing and workload-management practices highlighted here are likely to draw renewed scrutiny from regulators like the DGAC and EASA. Pilots operating into similar dual-use airports — where fighter jets, business aviation, airline traffic, and flight training coexist on shared infrastructure — should treat this case as a reminder that ATC service levels can vary significantly hour to hour even at internationally recognized airports, and that the ultimate responsibility for runway safety is a shared one between controllers and flight crews, not something to be delegated entirely to the tower.

Read original article