NYC96LA122 · Mooney M20K
Mooney M20K · Accident: loss of control in flight during landing
From Danbury Municipal Airport (DXR) to Danbury Municipal Airport (DXR)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC96LA122
- 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
- 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 M20K Possible conflict
- 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
- N11637
- Operator
- Vito E. Palermo · private individual
- Onboard fatalities
- Unknown
- Route
- From Danbury Municipal Airport (DXR)To Danbury Municipal Airport (DXR)
- 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
- Landing · aborted
- 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
- 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
- Airspeed › Inadequate
- Other crewmember › Raising of flaps, premature
Approximate · Estimated position: the centre of Danbury, CT, the place the record names. Not the accident site.
NTSB narrative
The pilot was returning from an instrument proficiency flight with a certificated flight instructor acting as the safety pilot. During the landing, the airplane bounced three times, and the pilot added full power to perform a go-around. The safety pilot stated that during the go-around 'In a panic to gain altitude, I raised the flaps, since the indicator was indicating full flaps. . . . The aircraft lost altitude, crashing into five aircraft which were parked on the ground.' Examination of the airplane did not disclose evidence of a malfunction, nor did either pilot report any. The FAA Flight Training Handbook stated for go-arounds (rejected landings), 'Depending on the airplane's altitude and airspeed, it may be wise to retract the flaps intermittently in small increments to allow time for the airplane to accelerate progressively as they are being raised. A sudden and complete retraction of the flaps at a very low airspeed could cause a loss of lift resulting the airplane settling into the ground.'
Probable cause
the safety pilot's raising of the flaps, while the airplane was at an inadequate airspeed during the aborted landing, which resulted in a stall, uncontrolled descent, and subsequent collision with parked airplanes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC96LA122
- Event ID
- 20001208X06086
- Case number
- NYC96LA122
- 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: 54ce03e2f0c3c75ddcee745920eb6e869d32d70343da0c65271931f4be9f2585; retrieved 2026-09-21T21:46:35.052Z.