American Eagle Aerospatiale ATR-72-212 accident
Aerospatiale ATR-72-212 · Accident: abrupt maneuver en route
From Lynden Pindling International Airport (NAS) to Fort Lauderdale Hollywood International Airport (FLL)
Event
- NTSB case
- MIA99LA039
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aerospatiale ATR-72-212
- Aircraft type
- Aerospatiale ATR-72
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N414WF
- Operator
- American Eagle
- Onboard fatalities
- Unknown
- Route
- From Lynden Pindling International Airport (NAS), NASSUATo Fort Lauderdale Hollywood International Airport (FLL)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Abrupt maneuver
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight was at 4,000 feet when Air Traffic Control gave the crew a traffic report. The crew could not locate the traffic, because at the time they were flying in instrument meteorological conditions. About 3 minutes later the crew received a TCAS (traffic collision avoidance system) alert to climb. The flight climbed from 4,000 feet and leveled off at 5,300 feet. During the climb both flight attendants fell. One flight attendant broke her leg, the other was not injured. The flight attendants were standing completing their pre-landing duties when the event occurred. The pilot radioed ATC that he needed to have an ambulance meet the flight when it landed. The flight landed without further incident, and the flight attendant was taken to a local hospital.
Probable cause
an abrupt maneuver in response to a traffic avoidance system alert, resulting in a flight attendant falling and breaking a leg.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99LA039
- Event ID
- 20001211X11597
- Case number
- MIA99LA039
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, damage. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: addbd4c5922fe531cb92b175b00209611ea1c9cc9b712c9867e4a248429848ff; retrieved 2026-09-18T17:02:06.292Z.
- The NTSB's operator name is blank for N414WF; the operator shown is the name the NTSB records it doing business as.