Pacific States Charter Service Cessna 401A accident
Cessna 401A · Accident: in flight collision with object on approach
From Tri Cities Airport (PSC) to Spokane International Airport (GEG)
Event
- NTSB case
- SEA96FA040
- 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
- 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
- Charter & commuter
- 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 401A
- Aircraft type
- Cessna 401
- 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
- N117AC
- Operator
- Pacific States Charter Service
- Onboard fatalities
- Unknown
- Route
- From Tri Cities Airport (PSC), Pasco, WATo Spokane International Airport (GEG)
- 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 135: Air Taxi & Commuter
- 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
- Approach · IFR final approach
- 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
- In flight collision with object
- 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
- Pole
- 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 › IFR procedure, not followed
- Pilot in command › Missed approach, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot (plt) received abbreviated weather (wx) briefing for emergency medical service (EMS)/air ambulance flight (flt). Before flt, he expressed anxiety about possible low visibility for landing & timely transport of dying patient. During ILS runway 3 approach (rwy 3 apch), aircraft (acft) remained well above the glide slope until close to the middle marker; acft's speed decreased from 153 to 100 kts, while vertical speed increased from 711'/min to about 1,250'/min descent. About 1 mi from rwy & 500' agl (in fog), acft abruptly turned left of localizer course & gradually descended with no distress call from plt. Acft hit a pole, then flew into a building & burned. Low ceiling, fog & dark night conditions prevailed. Plt (recent ex-military helicopter plt) had logged/reported 3500 hrs of flt time & about 150 hrs in multiengine airplanes, but there was evidence he lacked experience with actual instrument apchs in fixed-wing acft; he had difficulty with instrument flying during recent training & FAA check flts. No preimpact mechanical problem was found with acft/engines. No ILS anomalies were found. Flt nurse was using cellular phone, but no evidence was found of interference with acft's navigational system. Visibility & ceiling at destination were less than forecast at time of plt's preflt wx briefing. Paramedic was only survivor.
Probable cause
failure of the pilot to follow proper IFR procedures, by failing to maintain proper alignment with the localizer course during the ILS approach and/or by failing to follow the proper missed approach procedure. Factors relating to the accident were: darkness; adverse weather conditions; and pressure on the pilot to complete the EMS flight, due to the circumstances and conditions that prevailed.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA96FA040
- Event ID
- 20001208X05198
- Case number
- SEA96FA040
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-01-09.
- API snapshot SHA-256: be6f8e10f34c84cc6d7ccf8881448662b897c83870d3d8a29bad58741c21655e; retrieved 2026-09-18T13:39:31.855Z.