FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA03FA045 · Cessna 501

15 Mar 2003 · Carey, ID, United States

Cessna 501 · Accident: loss of control in flight en route

From Salt Lake City International Airport (SLC) to Friedman Memorial Airport (SUN)

Report a problem

Event

NTSB case
SEA03FA045
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
3 · 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
Instrument Meteorological Cond

Cessna 501

Aircraft type
Cessna 501
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
N70FJ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Salt Lake City International Airport (SLC), Salt Lake City, UTTo Friedman Memorial Airport (SUN), Hailey, ID
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 · 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 › Incapacitation

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

NTSB narrative

At 1407:11 the flight was cleared from Flight Level (FL) 240 to descend and maintain FL 190. At 1409:08 the controller cleared the flight to descend and maintain 15,000 feet, and at 1409:17 the pilot read back the clearance in its entirety. At 1410:20 the controller instructed the pilot to expedite his descent through 16,000 feet for traffic; however, there was no response. From 1410:33 to 1417:21 the controller made ten attempts to contact the pilot; again, there was no response. At 1417:26 the controller requested the pilot to ident if he could still hear him. At 1417:38 the controller received an ident from the aircraft and instructed the pilot to descend and maintain 15,000 feet. At 1418:36 the controller cleared the aircraft for the GPS approach and to acknowledge with an ident. There was no response. The aircraft had impacted a rocky drainage trench near the base of rock outcropping on a magnetic heading of 200 degrees in a wings level, approximately 40-degree nose down attitude, 15 nautical miles east-southeast of the destination airport at an elevation of 5,630 feet mean sea level. An examination of the aircraft's flight control, pressurization, and electrical systems revealed no anomalies with these systems which would have precluded normal operations. A further examination of the thermal damage to the aircraft, determined that there was no evidence of an inflight fire. Both engines underwent a complete teardown examination revealing no evidence of catastrophic or preaccident failure, and that both engines were functioning at the time of impact. Radar data revealed the aircraft was in level flight at FL 190 for more than 4 minutes, when it had previously been cleared to 15,000 feet. It subsequently began a climb reaching an altitude of 20,300 feet before beginning a right descending turn followed by a left descending turn. The last radar return before radar contact was lost indicated the aircraft was at 15,900 feet and descending. No evidence was available that suggests icing greater than light rime icing was present in the area and that weather was unlikely to have been a factor in the accident. The pilot was on two medications for high blood pressure and one for high cholesterol. The pilot had recently been found to have an elevated blood sugar, suggesting early diabetes or some other systemic disease or injury. The pilot had a family history of heart disease and high blood pressure, and had at least one episode of chest tightness in the past. It is possible that he had some unrecognized heart disease. The circumstances of the accident suggest substantial impairment or incapacitation of the pilot. It is possible that the pilot experienced an event such as a stroke or heart attack related to his previous medical conditions or as a new occurrence. It is also possible that he became hypoxic as a result of a decompression event without using supplemental oxygen. There is insufficient information to conclude any specific cause for the pilot's impairment or incapacitation.

Probable cause

Pilot incapacitation for unknown reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA03FA045
Event ID
20030325X00385
Case number
SEA03FA045
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, 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: c733f3005a3b97ef2c779c126c37948085c04975525cc475f7df498b6f0d8803; retrieved 2026-09-20T19:24:02.824Z.