DEN01LA007 · Piper PA-34-200T
Piper PA-34-200T · Accident: in flight collision with terrain/water on approach
From City of Colorado Springs Municipal Airport (COS) to Northern Colorado Regional Airport (FNL)
Event
- NTSB case
- DEN01LA007
- 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
Piper PA-34-200T
- Aircraft type
- Piper PA-34
- 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
- N238Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From City of Colorado Springs Municipal Airport (COS), COLO. SPRINGS, COTo Northern Colorado Regional Airport (FNL)
- 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
- Approach · IFR final approach
- 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
- In flight collision with terrain/water
- 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
- Pilot in command › IFR procedure, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was executing an ILS approach to an uncontrolled airport in low visibility conditions. He had his landing light and strobe lights on and failed to activate the pilot controlled runway lights. When his passenger informed him she saw lights, he went visual and could not see either the ground or runway environment. The aircraft drifted right and impacted the ground approximately 800 feet right and 1,000 feet down the runway. The landing gear collapsed and the aircraft slid to a stop on a taxiway adjacent to the ramp area.
Probable cause
Failure by the pilot to follow instrument approach procedures and execute a missed approach when the runway environment was not in sight at decision height. A factor was low ceiling.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN01LA007
- Event ID
- 20001212X22143
- Case number
- DEN01LA007
- 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: 975ce51fa573238128505adb4585b68dfd26a4ddc0cf9aa6924def374fabc06f; retrieved 2026-09-22T12:21:29.229Z.