Skip to content

Florida Files · from public records

Airbus in Florida NTSB files

NTSB aviation investigations in the shipped 2015 through 2024 Florida files that name Airbus as an aircraft make. A record can name more than one aircraft. This page does not refresh.

19
Airbus investigations, 2015-2024
0
deaths in those NTSB records
0
investigations with a death

Investigations in the closed-year files

Counts are totaled from the death figures in those files. A docket link appears when the file marks the case finished. Each row links to its case file.

Orlando: Airbus A320-232

1 serious

Probable cause: The captain’s inadvertent aggressive application of the brakes during taxi which resulted in a sudden stop. Contributing to the accident was the flight attendants’ failure to notify the flight crew of the unsecure cabin.

July 17, 2024 · NTSB DCA24LA241 · Case file · NTSB docket · Map

Jacksonville: Airbus A320

No deaths recorded

Probable cause: The loss of both Integrated Drive Generators (IDG) due to worn fixed cylinder block bores, which caused the IDGs to be tripped offline and caused the airplane to enter an emergency electrical configuration.

August 3, 2023 · NTSB ENG23LA033 · Case file · NTSB docket · Map

Fort Lauderdale: Airbus A320-214

1 serious

Probable cause: The flight crew’s abrupt change in pitch in response to a traffic collision advisory system resolution advisory that resulted in a serious injury to a flight attendant.

July 23, 2023 · NTSB DCA23LA395 · Case file · NTSB docket · Map

Sarasota: Boeing 737-823; Airbus 321

No deaths recorded

Probable cause: The local controller’s failure to prioritize and properly monitor the runway and airport environment along with his erroneous assumption that ROU 1633 would depart from runway 14 before AAL2172 arrived to land on the same runway, which resulted in a loss of separation between both airplanes.

February 17, 2023 · NTSB DCA23LA179 · Case file · NTSB docket · Map

St Petersburg-Clearwater: Airbus A319-112; Cessna M337B

No deaths recorded

Probable cause: The air traffic controller’s failure to properly scan the runway and local area, and their general loss of situational awareness, resulting in a near midair collision. Contributing to the incident was the Cessna 337 pilot's poor decision making when he failed to fly the standard downwind leg distance from the runway...

April 29, 2021 · NTSB OPS21LA002 · Case file · NTSB docket · Map

Orlando: Airbus A321

No deaths recorded

Probable cause: Encountering gusty conditions at a low altitude during landing and the crew’s decision to do a go-around at a low altitude with an excessive rotation rate.

August 8, 2019 · NTSB DCA19LA193 · Case file · NTSB docket · Map

Fort Lauderdale: Airbus A320

1 serious

Probable cause: A buildup of pressure in the coffee filter package resulting in the release of hot coffee and grounds when the pot locking lever was raised.

May 28, 2019 · NTSB DCA19CA153 · Case file · NTSB docket · Map

Miami: Airbus A320

No deaths recorded

Probable cause: the incorrect latching of the #2 Engine Fan Cowl following a routine maintenance check that resulted in separation of the cowl during takeoff.

September 19, 2016 · NTSB ENG16IA037 · Case file · NTSB docket · Map

Fort Lauderdale: Airbus A321 231

No deaths recorded

Probable cause: The air traffic controller's failure to ensure the runway surface area was clear of vehicles before clearing an aircraft for takeoff. Also causal was the flight crew's decision to initiate a takeoff while the Runway Status Lights (RWSL) Takeoff Hold Lights (THLs) were activated. Contributing to the incident was the...

January 29, 2016 · NTSB OPS16IA004 · Case file · NTSB docket · Map

More

Source: shipped NTSB aviation year files for 2015 through 2024. This page does not refresh. This Is Florida is not affiliated with any government agency.

Independent Florida resource built from public government records.