NYC03LA198 · Mooney M20A
Mooney M20A · Accident: in flight collision with object on approach
From Rockford, OH (no airport) to Rockford, OH
Event
- NTSB case
- NYC03LA198
- 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
Mooney M20A
- Aircraft type
- Mooney M20
- 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
- N1072B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rockford, OH (no airport)To Rockford, OH
- 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
- Approach
- 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 collision with object
- 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
- Wire, static
- 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
- Owner/builder › Planning/decision, improper
- Pilot in command › Altitude/clearance, 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 airplane was owned by the pilot's father-in-law, who maintained a 1,400-foot grass runway at his residence. A witness observed the airplane circling above the runway. He stated that the airplane appeared to be attempting to land, when it struck a utility wire and descended into the ground. The witness added that he did not hear any "sputtering" or unusual engine noises prior to the accident. The airplane was destroyed by a post crash fire. Examination of airman certificate records revealed that the pilot did not posses any airman certificates. Both the pilot and owner failed to provide any information regarding the circumstances of the accident, or the airworthiness history of the airplane, despite requests by both the Safety Board and the Federal Aviation Administration.
Probable cause
The pilot's failure to maintain the proper altitude/clearance, which resulted in an in-flight collision with a utility wire. The owner's improper decision to allow the airplane to be operated by an uncertificated pilot was also causal.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC03LA198
- Event ID
- 20030917X01550
- Case number
- NYC03LA198
- 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: 25c45e8eea5bf6505b72fd45ee4e5b2924ae5c2b20c406dcda28a943923ecf0b; retrieved 2026-09-21T09:23:03.117Z.