SEA08CA121 · Extra Flugzeugbau EA300/L
Extra Flugzeugbau EA300/L · Accident: hard landing
From Miles City Airport - Frank Wiley Field (MLS) to Great Falls International Airport (KGTF)
Event
- NTSB case
- SEA08CA121
- 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
Extra Flugzeugbau EA300/L
- Aircraft type
- Extra EA300
- 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
- N272X
- Operator
- David I Heaps · private individual
- Onboard fatalities
- Unknown
- Route
- From Miles City Airport - Frank Wiley Field (MLS), Miles City, MTTo Great Falls International Airport (KGTF), Great Falls, MT
- 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 pilot reported that as he approached the airport, he was unable to see the runway due to the sun being low on the horizon until he was on a close left base for the 10,502 foot-long runway. The pilot stated that he was faster than normal as he leveled the airplane to make a wheel landing about halfway down the runway. Upon touchdown, the airplane bounced and became airborne. As it settled back onto the runway, the main landing gear collapsed. The airplane veered to the left, struck a taxiway sign, and came to rest upright, adjacent to the runway. Examination of the airplane revealed that the undercarriage attach points in the fuselage sustained structural damage, and the right main landing gear was separated. No mechanical anomalies with the airframe or engine were reported.
Probable cause
The pilot's misjudged landing flare. A contributing factor was the glare from the sun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA08CA121
- Event ID
- 20080528X00740
- Case number
- SEA08CA121
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2008-05-04.
- API snapshot SHA-256: a957840f30fed89a6835ecc0a7ce51e2a4702e290f0d7ad5de26e4ff4fb6144d; retrieved 2026-09-15T09:41:42.068Z.