MIA03CA132 · Parsons Trainer
Parsons Trainer · Accident: loss of control in flight during initial climb
From New Smyrna Beach Municipal Airport (KEVB) to an unrecorded destination
Event
- NTSB case
- MIA03CA132
- 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
- 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
Parsons Trainer
- Aircraft type
- Parsons TRAINER
- Category
- Gyroplane
- 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
- UNREG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From New Smyrna Beach Municipal Airport (KEVB), New Smyrna, FLTo 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
- Initial climb
- 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
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Aircraft control, 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 student pilot stated that during initial takeoff, the aircraft climbed too fast, too early, and rolled to the right. He partially recovered prior to the aircraft colliding with the ground on the right side. A witness stated he observed the aircraft taking off on runway 6. About 1/3 of the way down the runway the aircraft rotated to a high angle of attack. The aircraft then yawed violently to the right. The pilot made a partial recovery but the aircraft again yawed to the right. The main rotor blades contacted the ground and the aircraft crashed. Post crash examination of the aircraft showed no evidence of malfunction. The aircraft was displaying FAA registration number N2059B at the time of the accident. FAA records indicate that the number was not currently assigned to an aircraft. The student pilot was not endorsed for solo flight.
Probable cause
Failure of the pilot to maintain control of the gyrocopter.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03CA132
- Event ID
- 20030711X01073
- Case number
- MIA03CA132
- 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: efb40c1afba6da06ae935099940dab3a939726a98bce6abeb874d4d64cc52eb0; retrieved 2026-09-21T19:26:31.021Z.