NYC01LA042 · Piper PA-28-161
Colgan Air Services Piper PA-28-161 · Accident: overrun during landing
From Youngstown Warren Regional Airport (YNG) to La Crosse Regional Airport (LSE)
Event
- NTSB case
- NYC01LA042
- 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
- Visual Meteorological Cond
Piper PA-28-161
- Aircraft type
- Piper PA-28
- 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
- N1305H
- Operator
- Colgan Air Services
- Onboard fatalities
- Unknown
- Route
- From Youngstown Warren Regional Airport (YNG), Youngstown, OHTo La Crosse Regional Airport (LSE), La Crosse, WI
- 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
- Substantial
Cause areas
- Pilot in command › Proper touchdown point, not obtained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The non-instrument rated pilot stated that he obtained a weather briefing from flight service prior to departure, and the forecast was for marginal VFR conditions. About 1 hour into the flight, the pilot experienced deteriorating weather conditions, including lowering visibility and rain. He made a 180-degree turn and diverted to an airport. The pilot landed long on Runway 27, but did not want to go-around in the deteriorating weather conditions. The airplane traveled off the end of the runway, into a ditch. Review of the pilot's weather briefing revealed that he was advised of cloud layers up to 25,000 feet along his planned route of flight, and AIRMETs for IFR conditions. About the time of the accident, the reported weather at an airport approximately 25 miles away was: wind from 100 degrees at 11 knots; visibility 1 3/4 statute mile; light rain and mist; ceiling 500 feet broken, 3,300 feet overcast; temperature 39 degrees Fahrenheit, dewpoint 37 degrees; altimeter 29.92 inches Hg.
Probable cause
The pilot's failure to obtain a proper touchdown point while landing. Factors were the pilot's improper weather evaluation, rain, a low ceiling, and a tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01LA042
- Event ID
- 20001215X45428
- Case number
- NYC01LA042
- 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: 5a3b92d725f6f01c8b49ccf4bc44ec441be77fadb97c158afb0a280ff6bf3058; retrieved 2026-09-21T20:02:35.935Z.