FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA82FA088 · Mooney M2OJ

29 Mar 1982 · Ormond Beach, FL, United States

Mooney M2OJ · Accident: in flight encounter with weather en route

From Ormond Beach, FL to Jacksonville, FL

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
MIA82FA088
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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Mooney M2OJ

Aircraft type
Mooney M2
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
N1118R
Onboard fatalities
Unknown
Route
From Ormond Beach, FLTo Jacksonville, FL
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
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
In flight encounter with weather
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 › Flight into known adverse weather, continued
  • Pilot in command › Judgment, poor
  • Pilot in command › Lack of total instrument time
  • Pilot in command › Procedures/directives, improper use of
  • Pilot in command › Spatial disorientation

Approximate · Estimated position: the centre of Ormond Beach, FL, the place the record names. Not the accident site.

NTSB narrative

THE NON-INSTRUMENT RATED PILOT HAD FILED FOR AN IFR CLIMB TO VFR-ON-TOP. HE TOOK OFF AFTER RECEIVING A CLEARANCE TO THE BULLI INTERSECTION WITH INSTRUCTIONS TO MAINTAIN 9000 FT, IF NOT VFR-ON-TOP BY THAT ALTITUDE. AT 1720 EST, THE PILOT TRANSMITTED THAT HE WAS INITIATING A TAKEOFF. HE CALLED DAYTONA BEACH DEPARTURE CONTROL WHILE CLIMBING AND RADAR CONTACT WAS ESTABLISHED AT 1722 EST. AT 1724, HE REPORTED CLIMBING THROUGH 1600 FT; HOWEVER, ABOUT ONE MINUTE LATER, RADIO AND RADAR CONTACT WERE LOST. GROUND WITNESSES REPORTED OBSERVING THE AIRCRAFT ABOUT ONE MILE FROM THE DEPARTURE AIRPORT AT LOW ALTITUDE. SUBSEQUENTLY, THE AIRCRAFT CRASHED IN A WOODED AREA WHILE IN A NEAR VERTICAL FLIGHT PATH. A TREE TRUNK WAS FOUND BELOW THE WRECKAGE PATH THAT HAD BEEN CUT IN THREE PIECES. THE CUT MARKS WERE CONSISTENT WITH DAMAGE FROM A PROPELLER AT HIGH POWER. NO PREIMPACT MALFUNCTION OR FAILURE OF THE AIRCRAFT WAS EVIDENT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MIA82FA088
Event ID
20020917X02408
Case number
MIA82FA088
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: 7cddadb5f7b9af9127d5a3b4c38900287dbff4e6673ecc24389f874943de4c66; retrieved 2026-09-21T08:33:37.391Z.