MIA87FA191 · Rockwell 690A
Rockwell 690A · Accident: abrupt maneuver en route
From Jacksonville International Airport (JAX) to Hartsfield Jackson Atlanta International Airport (ATL)
Event
- NTSB case
- MIA87FA191
- 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
- 2 · 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
- Charter & commuter
- 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
Rockwell 690A
- Aircraft type
- Rockwell 690
- 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
- N57169
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jacksonville International Airport (JAX), Jacksonville, FLTo Hartsfield Jackson Atlanta International Airport (ATL), ATLANTA, GA
- 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 135: Air Taxi & Commuter
- 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 · climb to 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
- Destroyed
Cause areas
- Pilot in command › Aerobatics, performed
- Pilot in command › Altitude, not maintained
- Pilot in command › Design stress limits of aircraft, exceeded
- Pilot in command › Directional control, not maintained
- Pilot in command › Overconfidence in personal ability
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
RADAR DATA INDICATED THE ACFT CLIMBED NORMALLY TO 9,200 FEET AT WHICH TIME SOME MANUEVER WAS PERFORMED WITH THE ACFT. THE ACFT THEN ENTERED A NEAR VERTICAL DIVE AND THE LAST RADAR HIT WAS AT 6,900 FEET. EXAMINATION OF THE ACFT REVEALED IT EXPERIENCED AN INFLIGHT STRUCTUAL BREAKUP AND THERE WAS NO EVIDENCE TO INDICATE PREBREAKUP FAILURE OR MALFUNCTION OF THE ACFT STRUCTURE, FLIGHT CONTROLS, ENGINES, ENGINE MOUNTS, AUTOPILOT, OR SYSTEMS. THE OPERATOR REPORTED ONE EMPLOYEE OVERHEARD THE PLT AND PASSENGER TALK ABOUT ROLLING THE ACFT PRIOR TO DEPARTURE, AND TWO COMPANY EMPLOYEES REPORTED BEING ONBOARD WHEN THE PILOT HAD ROLLED IT ON PRIOR OCCASIONS. ONE OF THESE WAS AT NIGHT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA87FA191
- Event ID
- 20001213X31255
- Case number
- MIA87FA191
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- 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. 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: 901fb4909dc34ef5ff25f2ef46d3595c9b6ff2f52beae889d679f431c6db187e; retrieved 2026-09-18T14:14:09.413Z.