NYC04LA209 · Cirrus Design Corp. SR-22
Cirrus Design Corp. SR-22 · Accident: loss of control on ground/water during landing
From Morristown Municipal Airport (MMU) to Waterbury Oxford Airport (OXC)
Event
- NTSB case
- NYC04LA209
- 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
Cirrus Design Corp. SR-22
- Aircraft type
- Cirrus SR-22
- 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
- N579AL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Morristown Municipal Airport (MMU), Morristown, NJTo Waterbury Oxford Airport (OXC), Oxford, CT
- 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 · flare/touchdown
- 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 on ground/water
- 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 › Recovery from bounced landing, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the landing, the airplane touched down to the left of the runway centerline, and bounced once before it departed the left side of the runway. The pilot then decided to abort the landing, but did not retract the flaps from the landing position. As the airplane accelerated, the pilot felt that it was not climbing as he expected it should, so he aborted the go-around attempt. The airplane touched down again on the grass, and subsequently struck a parked vehicle during the landing roll out. When asked how the accident could have been prevented, the pilot stated, "The go around procedure probably should not have been executed. Although the plane slid left, cutting the power would have probably resulted in [the airplane] resting in the grass."
Probable cause
The pilot's improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC04LA209
- Event ID
- 20040928X01504
- Case number
- NYC04LA209
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-09-12.
- API snapshot SHA-256: a9e83328259ad806b31151cc9209bc7737e436f3c8a64c2618bc700cd0e90491; retrieved 2026-09-22T06:43:33.199Z.