United Express Convair 580 accident
Convair 580 · Accident: on ground/water collision with object during landing
From Denver International Airport (DEN) to Durango La Plata County Airport (DRO)
Event
- NTSB case
- DEN88FA061
- 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
- Airline
- 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
Convair 580
- Aircraft type
- Convair 580
- 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
- N5808
- Operator
- United Express
- Onboard fatalities
- Unknown
- Route
- From Denver International Airport (DEN), Denver, COTo Durango La Plata County Airport (DRO), Durango, CO
- 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 121: Air Carrier
- 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 › Airport snow removal, inadequate
- Pilot in command › Proper alignment, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER MAKING AN IFR APPROACH, THE PILOT MADE A GO-AROUND BECAUSE HE WAS BLINDED BY THE REFLECTION OF THE LANDING/TAXI LIGHTS AGAINST THE FALLING SNOW. THE PILOT LANDED THE AIRCRAFT AFTER THE SECOND APPROACH. THE PILOT SAID HE SENSED THE AIRCRAFT DRIFTING TO THE LEFT AND HE TRIED TO CORRECT, BUT IT COLLIDED WITH A SNOW BANK. THE INVESTIGATION DISCLOSED NO EVIDENCE OF AIRCRAFT HYDROPLANING OR SKIDDING. AIRPORT MANAGEMENT ELECTED TO DELAY PLOWING THE RUNWAY FOR FEAR OF IT FREEZING OVER. PASSENGERS CLAIMED THERE WAS 2-3 INCHES OF SNOW ON TOP OF A 3/4- INCH LAYER OF SLUSH. FURTHER INVESTIGATION REVEALED THAT THE RUNWAY LIGHTS WERE OF VARIOUS INTENSITIES BECAUSE SOME UNAPPROVED LIGHT BULBS OF DIFFERENT AMPERAGE WERE USED. THE RUNWAY WAS NOT EQUIPPED WITH CENTERLINE LIGHTING. THE PAINTED WHITE CENTERLINE STRIPE WAS COVERED BY SNOW AND SLUSH.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN88FA061
- Event ID
- 20001213X25043
- Case number
- DEN88FA061
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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 1988-02-03.
- API snapshot SHA-256: 6810b356ae0b3a85c7d01b40012bbbed4085dbc5c79e19a2205d11e556dd7ae1; retrieved 2026-09-18T19:28:14.099Z.
- The NTSB's operator name is blank for N5808; the operator shown is the name the NTSB records it doing business as.