SEA07CA232 · Cirrus Design Corp. SR22
Cirrus Design Corp. SR22 · Accident: hard landing
From North Las Vegas Airport (VGT) to Montgomery-Gibbs Executive Airport (MYF)
Event
- NTSB case
- SEA07CA232
- 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. SR22
- Aircraft type
- Cirrus SR22
- 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
- N336SR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From North Las Vegas Airport (VGT), North Las Vegas, NVTo Montgomery-Gibbs Executive Airport (MYF), San Diego, CA
- 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
- Hard landing
- 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 › Porpoise/pilot-induced oscillation, encountered
- 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
According to the pilot, his landing approach was "a little low" so he added power to compensate. Upon touchdown, the airplane bounced "much higher" then he had previously experienced. He increased airspeed in an attempt to "make a more controlled landing." The airplane touched down and bounced "even higher." The airplane touched down a third time, and the nose wheel collapsed. Examination of photographs revealed structural damage to the bottom of the fuselage aft of the firewall.
Probable cause
The pilot's improper recovery from a bounced landing, which resulted in porpoising and collapse of the nose landing gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07CA232
- Event ID
- 20070912X01384
- Case number
- SEA07CA232
- 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: 560c3310910212dd2c3aba9d6f78d02d32e0ddb42144a125b12a1db8907bfaef; retrieved 2026-09-22T03:32:23.811Z.