MIA97LA052 · Sirocco Flying Club MJ 5
Sirocco Flying Club MJ 5 · Accident: loss of control in flight while maneuvering
From Orlando Sanford International Airport (SFB) to an unrecorded destination
Event
- NTSB case
- MIA97LA052
- 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
- 1 · 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
- General aviation
- 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
Sirocco Flying Club MJ 5
- Aircraft type
- Sirocco Flying Club MJ-5
- 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
- N949EA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orlando Sanford International Airport (SFB)To not recorded
- 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 91: General Aviation
- 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
- Maneuvering
- 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- 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 › Airspeed, not maintained
- Pilot in command › Stall, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After takeoff, at about the time the pilot was turning crosswind, he transmitted on tower frequency, 'I lost it, I'm coming in.' The airplane was observed to pitch nose down and impact the ground. Examination of the airplane by an FAA inspector revealed no evidence of preimpact failure or malfunction of the flight controls. According to tower personnel, in the past [previous flight(s)], the pilot had advised the controller of an engine overheating problem, but no determination was made as to the reason for the previously reported engine overheating condition.
Probable cause
failure of the pilot to maintain adequate airspeed, while maneuvering in the traffic pattern (crosswind) after takeoff, which resulted in an inadvertent stall, uncontrolled descent, and collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA97LA052
- Event ID
- 20001208X07220
- Case number
- MIA97LA052
- 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: 3f8a1e2935d31267259248864c36e06c2e23db3276ab0f0c4c18d26419f6ff48; retrieved 2026-09-20T23:04:21.427Z.