FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA02LA134 · Champion 7ECA

13 Jul 2002 · Kittitas, WA, United States

Champion 7ECA · Accident: total loss of engine power (non-mechanical) en route

From Port of Whitman Business Air Center Airport (S94) to Norman Grier Field (S36)

Report a problem

Event

NTSB case
SEA02LA134
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

Champion 7ECA

Aircraft type
Champion 7
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
N9542S
Operator
Crawford, Gary N. · private individual
Onboard fatalities
Unknown
Route
From Port of Whitman Business Air Center Airport (S94), Colfax, WATo Norman Grier Field (S36), Kent, 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 · 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
Total loss of engine power (non-mechanical)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Fuel exhaustion
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

  • Fluid, fuel › Exhaustion
  • Pilot in command(cfi) › Aircraft preflight, inadequate

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 (front seat) accompanied by the individual (rear seat pilot) who had recently purchased the aircraft departed Colfax, Washington, en route to Kent, Washington. The amount of fuel available was not adequately verified by the pilot and after flying over 150 statute miles the aircraft's engine lost power and the pilot executed a forced landing on rocky terrain. The rear seat pilot reported that subsequent to the forced landing he checked the right wing fuel tank low point drain and observed only enough gas to moisten his thumb. A check of the left wing fuel tank low point drain yielded a steady stream of gas, but when he returned to the aircraft the following day to begin recovery procedures he was unable to siphon any gas from either tank. He also noted that there was no significant gas observed when the wings were removed from the airframe.

Probable cause

The pilot's failure to conduct an adequate preflight inspection of the fuel resulting in fuel exhaustion and a subsequent forced landing. A contributing factor was the rocky terrain encountered during the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA02LA134
Event ID
20020726X01224
Case number
SEA02LA134
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 2002-07-14.
  • API snapshot SHA-256: 4d5099223dda71cac2536e0e1cecfbf74bc78db6e3b351451546aa334b9d9234; retrieved 2026-09-22T10:43:47.296Z.