CEN24LA294 · Mooney M20J
Mooney M20J · Incident: ground collision while taxiing
Event
- NTSB case
- CEN24LA294
- 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
- Incident
- 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
- 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
Mooney M20J
- 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
- N555ED
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 46 years (built 1978)
- 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
- Taxi
- Defining eventThe 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
- Ground collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Environmental issues › Physical environment
- Personnel issues › Psychological
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 reported that while taxiing from a grass tiedown area, the airplane’s left wingtip struck the propeller of a parked airplane. She did not notice the wingtip strike, so she continued to taxi and obtained her instrument flight rules (IFR) clearance. After transitioning to the paved taxiway yellow centerline stripe, the airplane’s right wing tip struck the propeller of a second parked airplane. The pilot shut down the engine and exited the airplane to examine the damage. The airplane sustained minor damage to both wings. The incident occurred during the annual Experimental Aircraft Association AirVenture fly-in. The airport issued a Notice to Air Mission that was active at the time of the incident that advised operators “FBO RAMP, T HANGER RAMP PRKG NOT STD.” The pilot stated that it was not clear to her what this meant. The pilot recommended that additional personnel for wing walkers could have prevented the incident. According to the Aeronautical Information Manual, being centered on the taxiway centerline does not guarantee wingtip clearance with other aircraft or other objects.
Probable cause
The pilot’s failure to maintain adequate wingtip clearance while taxiing. Contributing to the accident was the ambiguous nonstandard parking at the time of the incident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA294
- Event ID
- 20240730194812
- Case number
- CEN24LA294
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 511c0bbd4f0bfe6c5b44c4e7b80d6b7e987e9dd43f17aac208436c56c69daae1; retrieved 2026-09-16T19:06:49.849Z.