CEN10CA167 · Cirrus Design Corp SR22
Lot-A-Go Five Cirrus Design Corp SR22 · Accident: abnormal runway contact during landing
From Corpus Christi International Airport (KCRP) to Sugar Land Regional Airport (KSGR)
Event
- NTSB case
- CEN10CA167
- 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
- N616CP
- Operator
- Lot-A-Go Five
- Onboard fatalities
- Unknown
- Route
- From Corpus Christi International Airport (KCRP), Corpus Christi, TXTo Sugar Land Regional Airport (KSGR), Sugar Land, TX
- 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
- 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was landing at a familiar airport at night. During the landing the pilot reported misjudging the runway landing zone and approached the runway with a steep descent. The airplane landed hard on the runway and bounced back into the air. The pilot reported that while back in the air, a crosswind pushed the airplane off of the 100-foot wide runway and the airplane touched down in the grass off of the runway. When the pilot applied power to go-around, the airplane's nosewheel dug into the soil and the airplane flipped inverted. The airplane's fuselage, empennage, and rudder received substantial damage. The pilot reported no mechanical anomalies with the airframe or engine prior to the accident. An examination of the airframe and engine by Federal Aviation Administration inspector did not reveal any preimpact anomalies. In addition, the pilot reported no problems with the airport facilities.
Probable cause
The pilot's failure to maintain a proper glidepath and rate of descent during approach, resulting in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA167
- Event ID
- 20100322X12809
- Case number
- CEN10CA167
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2010-03-22.
- API snapshot SHA-256: 862d91135a99e34899c27c73f7ce369ec3e0c954d471bedd80a457e303a09605; retrieved 2026-09-15T13:46:25.017Z.