Corporate Air Aero Commander 680FL accident
Aero Commander 680FL · Accident: loss of control in flight en route
From Seattle–Tacoma International Airport (SEA) to Spokane International Airport (GEG)
Event
- NTSB case
- SEA93FA046
- 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
- 1 · 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
- Unknown
Aero Commander 680FL
- Aircraft type
- Aero Commander 680
- 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
- N111MN
- Operator
- Corporate Air
- Onboard fatalities
- Unknown
- Route
- From Seattle–Tacoma International Airport (SEA), Seattle, WATo 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 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
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER DEPARTURE, THE AIRPLANE INTERCEPTED AIRWAY V-2, AND APPEARED TO CLIMB NORMALLY UNTIL REACHING 8300 FT (9000 ASSIGNED) WHILE TRACKING APRX 110 DEG MAG. RADAR ANALYSIS SHOWED THE AIRPLANE AT 128 KIAS WHEN IT ABRUPTLY TURNED LEFT 30 DEG AND THEN APPEARED TO RECOVER. VOICE COMMUNICATION DURING THIS EVENT WAS NORMAL WITH NO CHANGE IN THE PILOT'S LEVEL OF ANXIETY. IMMEDIATELY THEREAFTER, THE HEADING CHANGED OVER 90 DEG TO THE LEFT (NORTHBOUND), AND A MAXIMUM 6750 FPM RATE OF DESCENT DEVELOPED BEFORE THE HEADING STABILIZED AND THE DESCENT SLOWED. THE AIRPLANE'S GROUND IMPACT SITE WAS APRX 1 NM SW OF THE LAST RADAR TARGET. WRECKAGE DISTRIBUTION WAS ROUGHLY PARALLEL TO V-2. THE AIRPLANE IMPACTED THE MOUNTAINSIDE IN A STEEP NOSE LOW, LEFT WING DOWN ATTITUDE. THE ENGINES, PROPELLERS/GOVERNORS WERE DISASSEMBLED AND INSPECTED WITH NO EVIDENCE OF MECHANICAL MALFUNCTION. EXAM OF THE LEFT PROPELLER INDICATED LOW POWER ON IMPACT. THERE WAS NO EVIDENCE OF SIGNIFICANT ICING/TURBULENCE.
Probable cause
UNDETERMINED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA93FA046
- Event ID
- 20001211X16241
- Case number
- SEA93FA046
- 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 1992-12-26.
- API snapshot SHA-256: ca99020c1854dcc96b51294be6c3cee59c78585ef84d239db4bae89278f0eafa; retrieved 2026-09-18T13:54:30.496Z.