SEA95FA175 · Beech F33A
Beech F33A · Accident: loss of control in flight en route
From Cut Bank International Airport (CTB) to Spokane International Airport (GEG)
Event
- NTSB case
- SEA95FA175
- 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
- 2 · 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
- Unknown
Beech F33A
- Aircraft type
- Beechcraft 33
- 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
- N8014R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cut Bank International Airport (CTB), Cut Bank, MTTo Spokane International Airport (GEG), Spokane, WA
- 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
- En route · climb to cruise
- 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft control, uncontrolled
- Pilot in command › Incapacitation(cardiovascular)
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported via radio to Cedar City Flight Watch that he was VMC and climbing through 11,400 feet. Flight Watch provided weather information and approximately 1 minute later the pilot responded 'OK, roger that ah understand---.' A recording of this transmission revealed the pilot breathing heavily and forcefully and his rate of speech had slowed noticeably. Radar data at the time of this transmission showed the aircraft peaking in the climb and transitioning into a high rate of descent which continued until ground impact in mountainous terrain. Post-mortem examination revealed severe sclerosis with over 60% occlusion of the right artery and over 90% occlusion of the left anterior descending and circumflex branches. The examination revealed ankle fractures but no hand/wrist/finger fractures. The pilot was 36 years old and his twin brother reported a 'heart issue' 8-10 years earlier.
Probable cause
the pilot's incapacitation due to a heart attack.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA95FA175
- Event ID
- 20001207X04371
- Case number
- SEA95FA175
- 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: 3c15a3ee6c729dbb63cc4eb00fca34289be672e999dd0deec9fb54391a16805c; retrieved 2026-09-20T23:40:26.112Z.