DFW06LA060 · Cessna 175
Cessna 175 · Accident: hard landing
From Shawnee Regional Airport (SNL) to Lindsay Municipal Airport (1K2)
Event
- NTSB case
- DFW06LA060
- 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
Cessna 175
- Aircraft type
- Cessna 175
- 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
- N6612E
- Operator
- Kristopher E. Hoopes · private individual
- Onboard fatalities
- Unknown
- Route
- From Shawnee Regional Airport (SNL), Shawnee, OKTo Lindsay Municipal Airport (1K2), Lindsay, OK
- 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 › Airspeed, not maintained
- Pilot in command › Flare, high
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 156-hour private pilot stated that during a night flight, he allowed the airplane's airspeed to decrease while flaring too high, resulting in a hard landing. Upon impact with the runway, the upper portion of the firewall separated from the airframe causing the engine to drop downward approximately 30 degrees. A post-accident inspection revealed that the upper left engine support-mount had cracked at the bracket bolt hole, and that the upper right engine attachment rivets had separated from the airframe stringer assembly. The upper engine mount brackets were removed from the airplane and sent to the NTSB Materials Laboratory; the examination revealed that the brackets fractured due to fatigue. The examination also revealed that the metal content of the brackets did not contain the constituent elements of the specified material, and was approximately 40 percent below the specified strength.
Probable cause
The hard landing was the result of the pilot's failure to maintain adequate airspeed while misjudging the altitude above the runway. Contributing factors were the inadequate quality of the manufacturer's engine-support bracket and the prevailing night conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06LA060
- Event ID
- 20060213X00198
- Case number
- DFW06LA060
- 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 2006-01-26.
- API snapshot SHA-256: 76a2da3871f0e3fe1d5cecdac6cea36a619cd5949f436a763797edec816c83aa; retrieved 2026-09-22T05:08:23.915Z.