Investigations Raise Questions About FlySafair’s Transparency and Safety Compliance
FlySafair Flight FA 268 Near-Crash: What Really Happened?
A FlySafair Boeing 737 carrying passengers was moments away from disaster near Durban’s King Shaka International Airport on 27 June 2023. The flight, designated FA 268, experienced a drastic descent to just 105 meters above ground before the pilots managed to regain control. While FlySafair maintains that it complied with all safety reporting requirements, emerging details suggest a possible delay in reporting the incident, sparking concerns about transparency and regulatory oversight.
Delayed Reporting Raises Red Flags
Under South African aviation law, serious incidents must be reported within 24 hours by the airline, pilots, and Air Traffic and Navigation Services (ATNS). However, the SA Civil Aviation Authority (Sacaa) only became aware of the FA 268 incident months later, allegedly due to a whistle-blower tip-off.
According to FlySafair’s marketing manager, Kirby Gordon, the airline reported the incident on 25 August 2023 in line with regulations. However, Sacaa refuted this claim, stating that the official report only came on 18 September 2023, nearly three months after the event.
ATNS, which detected the flight’s erratic movements, did report the incident within the required timeframe. This discrepancy raises concerns about whether FlySafair deliberately withheld critical information.
Was Flight Data Erased?
Investigators also discovered that by the time FlySafair acknowledged the incident in September, the aircraft’s cockpit voice recorder and flight data recorder had been overwritten. This could have seriously compromised the investigation, making it difficult to determine the exact cause of the near-disaster.
Initially, Sacaa confirmed that vital flight data was lost, but later reversed its stance, stating that data had been downloaded and sent to Boeing for analysis. However, Boeing spokesperson Paul J. Lewis declined to comment, referring inquiries back to Safair and South African regulators.
Non-Disclosure Agreements & Alleged Cover-Up
According to a report on the FlyAfrica aviation forum, FlySafair’s pilots were allegedly forced to sign non-disclosure agreements (NDAs) regarding the incident. If true, this would suggest an attempt to suppress information about what really happened.
FlySafair denied these claims, but the timing of its report—after a whistle-blower stepped forward—raises concerns about the airline’s commitment to transparency.
Contradictory Statements & Safety Concerns
Despite clear public flight tracking data (FlightRadar24) showing FA 268’s uncontrolled descent, Sacaa classified the event as a “routine missed approach.” This contradicts expert opinions, with Boeing 737 Captain Duncan Gillespie calling the classification “highly questionable” given the severity of the descent and last-second recovery.
Sacaa initially did not publish FA 268’s report, despite making minor aviation incidents publicly available. It later revised its stance, calling the event a Part 140 occurrence, which only investigates airline safety protocols rather than specific flight safety violations.
Conclusion: A Need for Greater Transparency in Aviation
The FA 268 incident raises critical questions about aviation safety oversight in South Africa. If a serious near-crash could be delayed in reporting and its data allegedly erased, how many other incidents remain hidden from public scrutiny?
FlySafair has grown into one of South Africa’s most dominant budget airlines, but concerns about safety transparency could tarnish its reputation. With passengers trusting airlines to prioritize safety over corporate interests, this case underscores the need for stronger regulatory enforcement and greater accountability from airlines.
Also read: FlySafair’s Ownership Breach: Licensing Authority Warns of ‘Catastrophic’ Industry Impact
