Cascade Flight School Cessna 310N accident
Cessna 310N · Accident: in flight collision with object while maneuvering
From Tacoma Narrows Airport (TIW) to Bellingham, WA
Event
- NTSB case
- SEA88MA015
- 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
- 4 · 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
- Visual Meteorological Cond
Cessna 310N
- Aircraft type
- Cessna 310
- 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
- N4178Q
- Operator
- Cascade Flight School
- Onboard fatalities
- Unknown
- Route
- From Tacoma Narrows Airport (TIW), Tacoma, WATo Bellingham, 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 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
- Maneuvering
- 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
- Tree(s)
- 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 › Proper altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT WAS CHARTERED TO TAKE UNIVERSITY (WWU) PSNL TO AN ALUMNI DINNER. WHILE RTRNG AT NGT, THE PLT MADE A LOCALIZER ONLY, ILS RWY 16 APCH IN MARGINAL VFR CONDS. DRG THE APCH, RADAR SVC WAS TERMINATED & THE PLT WAS TOLD TO CTC BELLINGHAMRADIO, BUT HE DID NOT LND OR CTC THE FACILITY. RADAR DATA SHOWED HE CONTD SOUTHBOUND TWD WWU & CHGD THE TRANSPONDER CODETO 1200 (VFR). RADAR CTC WAS LOST FOR APRX 1-1/2 MIN AS THE ACFT PASSED OVR THE VCNTY OF WWU & 1 OF THE PAX'S HOME, THENRADAR CTC WAS REESTABLISHED. WITNESSES IN THE AREA RPRTD SEEING A LOW FLYING ACFT AT APRX THAT TIME. THE ACFT THEN FLEW TO THE VCNTY OF SVRL LARGE REFINERIES APRX 9 MI NNW OF THE ARPT & RADAR CTC WAS LOST AGAIN. WHEN THE ACFT DID NOT LAND AT THE ARPT, A SEARCH WAS STARTED. IT WAS FND WHERE IT HAD HIT 200' TREES & CRASHED. NO ONE SAW THE ACDNT, BUT 2 PERSONSSAW AN ACFT FLYING AT LOW ALT IN THAT VCNTY WITH THE LNDG LGT ON. THEY ALSO RPRTD PTCHY FOG IN THE AREA. SUBSEQUENTLY, THE ACFT TURNED TO AN EASTERLY HDG BFR IT CRASHED. NO PREIMPACT MECH PRBLM WAS FND THAT WOULD HAVE CAUSE THE ACDNT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA88MA015
- Event ID
- 20001213X32643
- Case number
- SEA88MA015
- 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 1987-11-05.
- API snapshot SHA-256: 1c5ff050aeb2d2f635bcac688cc3e47ab1b480eaed47003b2ea4373cc360fd07; retrieved 2026-09-18T14:12:53.103Z.