NYC01FA158 · Moravan Zlin 526F
Moravan Zlin 526F · Accident: loss of control in flight while maneuvering
From Easton Airport / Newnam Field (ESN) to an unrecorded destination
Event
- NTSB case
- NYC01FA158
- 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
- Unknown
- 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
Moravan Zlin 526F
- Aircraft type
- Moravan ZLIN 526
- 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
- N526GC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Easton Airport / Newnam Field (ESN), Easton, MDTo 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/spin
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot and passenger departed on a local aerobatic flight. A few minutes after becoming airborne, the airplane entered a local aerobatic training area. After completing several aerobatic maneuvers, including an immelmann, the pilot attempted a second immelmann. The pilot entered the maneuver, and the airplane climbed about 1,000 feet before completing the course reversal. While the airplane was at the top of the maneuver and inverted, the pilot applied right stick to roll the airplane to the upright position. As the airplane started to roll, the nose began "creeping" right, and then suddenly the airplane entered an inverted spin. The passenger bailed out, but the pilot remained with the airplane until impact. The pilot had approximately 7,000 hours of flight experience, and was actively flying aerobatics. No pre-impact failures or malfunctions were identified with either the engine or the airframe.
Probable cause
The pilot's failure to maintain airspeed during an aerobatic maneuver, which resulted in an inadvertent inverted spin.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01FA158
- Event ID
- 20010712X01402
- Case number
- NYC01FA158
- 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, coordinates. 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: 8bce233a7445a424d3f6fcf18c40dd083399041b8d5aa3a8656f0339d3958aea; retrieved 2026-09-20T20:28:54.144Z.