DCA86AA001 · Vickers VISCOUNT VC-810 VISCOUNT V
Vickers VISCOUNT VC-810 VISCOUNT V · Accident: overrun during landing
From Blue Grass Airport (LEX) to an unrecorded destination
Event
- NTSB case
- DCA86AA001
- 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
- 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
- Instrument Meteorological Cond
Vickers VISCOUNT VC-810 VISCOUNT V
- Aircraft type
- Vickers VISCOUNT VC-810
- 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
- N923RC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Blue Grass Airport (LEX), Lexington, KYTo not recorded
- 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
- Landing · landing roll
- 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 › In-flight planning/decision, improper
- Pilot in command › Missed approach, not performed
- Pilot in command › Proper touchdown point, exceeded
- Pilot in command › Visual/aural perception
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DRG AN ILS TO RWY 35, THE APCH WAS NORMAL UNTIL THE ACFT WAS APRX 100' ABV THE DECISION HEIGHT, EXCEPT THERE WAS CONDENSATION ON THE WINDSHIELD. TOUCHDOWN WAS HARD. A WITNESS SAID THE ACFT LNDD APRX 1/3 OF THE WAY DOWN THE 5200' RWY. AFTER LNDG, WITH THE PROPS IN 'GROUND FINE,' BRAKING ACTION WAS INEFFECTIVE ON THE WET RWY. THE ACFT WAS NOT EQUIPPED WITH AN ANTI-SKID BRAKING SYS. SUBSEQUENTLY, THE ACFT CONTD OFF THE RWY & WENT DOWN AN EMBANKMENT INTO A FIELD.SCRUB MARKS ON THE RWY & REVERTED RUBBER ON THE TIRES INDICATED THE ACFT WAS HYDROPLANING. ACCORDING TO THE FLT MANUAL, 4500' (PLUS A 10% FACTOR FOR NO ANTI-SKID) WOULD HAVE BEEN REQUIRED TO STOP ON A DRY RWY IN THE PREVAILING WX CONDS, WHICH INCLUDED A SLIGHT TAILWIND. TWO PAX, ACTING AS FLT ATTENDANTS (F/A'S), ASSISTED THE OTHER PAX IN EVACUATING. AN INVESTIGATION REVEALED THE F/A'S WERE NOT PROPERLY TRAINED; THE PAX WERE NOT COMPLETELY BRIEFED BEFORE THE FLT; & THE PAX BRIEFING CARDS WERE INADEQUATE. THE ACFT WAS ON A BUSINESS FLT TO TRANSPORT AN ENTERTAINMENT TROUPE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DCA86AA001
- Event ID
- 20001214X37995
- Case number
- DCA86AA001
- 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: af9d0acb17500ac29dbc2b945dd17229da8f646f77a7147a0608e541c2e14baa; retrieved 2026-09-21T17:07:42.536Z.