LAX86FVD03 · Aero Commander 680T
Aero Commander 680T · Accident: overrun
From an unrecorded airport to UNKNOWN
Event
- NTSB case
- LAX86FVD03
- 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
- 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
Aero Commander 680T
- 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
- N17690
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo UNKNOWN
- 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
- Unknown
- 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
- Overrun
- 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 › Impairment(alcohol)
- Pilot in command › Judgment, poor
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ON 12/3/85 AT APRX 0830, THE ACFT WAS FND LYING INVERTED IN A CANAL ADJACENT TO THE ARPT WHERE IT HAD BEEN ON 24 HR STANDBY FOR MEDICAL FLTS. TWELVE DAYS LATER, THE PLT'S BODY WAS ALSO FND IN THE CANAL. AN INVESTIGATION REVEALED THE ACFT HAD BEEN TAKEN SOMETIME DURING A PERIOD WHEN THE TOWER WAS CLOSED BETWEEN 2200 PST ON 12/2/85 & 0600 PST THE NEXT MORNING, WITHOUT THE KNOWLEDGE OR CONSENT OF THE OPERATOR. MAIN GEAR TIRE MARKS WERE FND IN MUD WHERE THE ACFT HAD CONTD OFF THE DEPARTURE END OF THE RWY. BEYOND THE END OF THE RWY, THE ACFT HIT A FENCE & A 5 FT DIRT BANK, THEN HIT THE GND AFTER BEING AIRBORNE ABOUT 200 FT & CAME TO REST IN THE CANAL. SHERIFF'S PSNL CONTACTED FRIENDS OF THE PLT, WHO HAD SPENT THE EVENING WITH HIM. BASE ON INFORMATION THAT THEY PROVIDED CONCERNING THE CONSUMPTION OF ALCOHOLIC BEVERAGES, THE SHERIFF'S PSNL STATED THAT THE PLT WOULD HAVE BEEN LEGALLY INTOXICATED. THE OVERRUN WAS PRESUMED TO HAVE OCCURRED DURING EITHER A LANDING OR A TAKEOFF ON 12/3/85.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX86FVD03
- Event ID
- 20001214X38433
- Case number
- LAX86FVD03
- 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. 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: 733044db91f4108ba3914e2604d344855bb628edbc4959d0b2300875486a275e; retrieved 2026-09-21T04:44:55.686Z.