FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW08CA083 · Cessna 150

16 Mar 2008 · Idabell, OK, United States Narrative disagrees

Idabel Broken Bow Paris Flying Club Cessna 150 · Accident: hard landing

From McCurtain Memorial Hospital Heliport (1OK4) to Idabell, OK

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
DFW08CA083
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 150

Aircraft type
Cessna 150
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
N554SP
Onboard fatalities
Unknown
Route
From McCurtain Memorial Hospital Heliport (1OK4), Idabel, OKTo Idabell, 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
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
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

  • Aircraft › Aircraft oper/perf/capability

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The student pilot overflew the runway, and checked the automated weather reporting station for the airport. The pilot stated that the station was reporting 27 to 35-knots sustained winds with gusts from 40 to 45-knots. The pilot then landed on runway 02 (a 5,000-foot by 75-foot asphalt runway) with 0-degrees of flaps. He added that during the flare, a gust of wind "picked-up" the right side of the airplane and subsequently the airplane dropped to the runway. Examination of the airplane revealed that the fuselage just aft of the engine mount attachment point was buckled.

Probable cause

The pilot's inadequate compensation for wind conditions. Factors contributing to the accident are high and gusting winds.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW08CA083
Event ID
20080401X00412
Case number
DFW08CA083
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: 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: aeabfc37e57f3ffb4cce61c9d06414fa4166f0c35a14356ab0c39537caf486ba; retrieved 2026-09-15T09:28:47.468Z.