BFO93LA039 · Cessna 335
Cessna 335 · Accident: on ground/water collision with object during landing
From Blue Grass Airport (LEX) to an unrecorded destination
Event
- NTSB case
- BFO93LA039
- 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
Cessna 335
- Aircraft type
- Cessna 335
- 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
- N26CP
- Operator
- Richard N Anderson · private individual
- 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
- On ground/water collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Airport personnel › Notams, not issued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT HE EXECUTED THE ILS APPROACH TO RUNWAY 35. THE RUNWAY WAS 6499 FEET LONG AND 150 FEET WIDE. HE SAID HE DESCENDED TO ABOUT 550 FEET ABOVE THE GROUND ON HIS APPROACH AND SAW THE RUNWAY LIGHTS. HE STATED THAT DURING THE LANDING ROLL, HE LOST SIGHT OF THE RUNWAY LIGHTS DUE TO FOG. ACCORDING TO THE FAA, IT WAS A DARK NIGHT WITH LOW LEVEL FOG AND HAZE. MOST OF THE RUNWAY HAD BEEN CLEARED, BUT SNOW REMAINED NEAR THE EDGES. THE LEFT SIDE WAS COVERED WITH SNOW FROM ABOUT 6 TO 14 FEET FROM THE LEFT EDGE. THE AIRPLANE ENCOUNTERED SNOW ON THE LEFT SIDE, WHERE SNOW ON AND ADJACENT TO THE RUNWAY WAS ABOUT 12 FEET WIDE. APPROACHING THE INTERSECTION WITH RUNWAY 5/23, THERE WAS A SNOWBANK ON THE LEFT EDGE THAT OBSCURED THE RUNWAY LIGHTS. AT THE INTERSECTION, THE SNOWBANK ROSE TO ABOUT 6 FEET TALL AND EXTENDED ABOUT 12 FEET ONTO THE RUNWAY 35. THE LEFT NACELLE STRUCK THE SNOWBANK, WHICH SPUN THE AIRCRAFT AND SHEARED OFF THE LANDING GEAR.
Probable cause
FAILURE OF AIRPORT PERSONNEL TO REPORT THE RUNWAY CONDITION BY NOTAM WHEN AIRPORT SNOW REMOVAL PERSONNEL LEFT SNOW PILED ON THE EDGES OF THE RUNWAY. FACTORS RELATED TO THE ACCIDENT WERE: DARK NIGHT, FOG, AND THE SNOWBANK.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA039
- Event ID
- 20001211X11917
- Case number
- BFO93LA039
- 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 1993-03-03.
- API snapshot SHA-256: d5645dbb0c4addb6d4f12e0801105c1eb7508c2dc1b3266998b0dc04647eaaaa; retrieved 2026-09-23T02:17:03.851Z.