CHI95LA199 · Cessna 310L
Cessna 310L · Accident: dragged wing, rotor, pod, float or tail/skid during landing
From CFJ to an unrecorded destination
Event
- NTSB case
- CHI95LA199
- 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
Cessna 310L
- Aircraft type
- Cessna 310
- 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
- N3298X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From CFJTo not recorded
- 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
- Dragged wing, rotor, pod, float or tail/skid
- 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 › Airspeed, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT TOOK OFF WITH THE INTENTION OF REMAINING IN THE AIRPORT TRAFFIC PATTERN TO PRACTICE THREE TAKEOFFS AND LANDINGS. THE PILOT STATED THAT HE DECIDED TO PRACTICE A POWER OFF LANDING FIRST. DURING THE FIRST LANDING THE PILOT HAD TO ADD POWER TO MAKE IT TO THE RUNWAY. DURING THE SECOND LANDING, THE PILOT STATED HE FLEW A TIGHTER PATTERN. WHILE ON FINAL APPROACH, HE HAD TO REALIGN THE AIRPLANE WITH THE RUNWAY. AT THIS POINT, THE AIRSPEED DROPPED RAPIDLY AND HE DECIDED TO PERFORM A GO AROUND. THE PILOT STATED THE LEFT WING IMPACTED THE RUNWAY, BUT HE HAD TO CONTINUE WITH THE GO AROUND DUE TO TRAFFIC. THE PILOT STATED A THIRD PATTERN WAS DONE USING NORMAL PROCEDURES AND HE LANDED THE AIRPLANE WITH NO FURTHER INCIDENT.
Probable cause
the pilot's failure to maintain adequate airspeed during final approach to landing. A factor in the accident was the pilot's delayed action of aborting the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI95LA199
- Event ID
- 20001207X03679
- Case number
- CHI95LA199
- 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: 2a6ad64a5a3c1c30f08f962e5f176491860b388d8ee7700ed829ca628239c1e6; retrieved 2026-09-22T23:46:02.927Z.