CHI06LA061 · Piper PA-32-300
Piper PA-32-300 · Accident: in flight collision with terrain/water during landing
From Scott City Municipal Airport (TQK) to Worthington Municipal Airport (OTG)
Event
- NTSB case
- CHI06LA061
- 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
- Unknown
- 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-32-300
- Aircraft type
- Piper PA-32
- 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
- N190PH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Scott City Municipal Airport (TQK), Scott City, KSTo Worthington Municipal Airport (OTG), Worthington, MN
- 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
- 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 › Directional control, not maintained
- Pilot in command › Missed approach, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane veered off the runway after touchdown following a precision instrument approach and landing on runway 29. Night visual meteorological conditions prevailed at the time of the accident. The pilot stated that the airport's automated weather observing system (AWOS) reported calm winds, but he felt that this was inaccurate so he checked reports from surrounding AWOSs, which reported winds from the northwest at 8-11 knots. The pilot stated that upon touchdown, the airplane moved "quickly" to the left and departed off the side of the runway and into snow, which folded the nose wheel landing gear. The maximum demonstrated cross wind for the airplane is 17 knots. Inspection of the airport's AWOS following the accident revealed that the AWOS was covered with ice, which inhibited operation of the wind speed and direction sensors. The Federal Aviation Administration had no record of a Notices to Airman being issued on the day of the accident pertaining to the airport AWOS.
Probable cause
The missed approach not performed by the pilot and the directional control not maintained by the pilot during landing. Contributing factors were the crosswind, wind information not available due to inoperative meteorological equipment, and a Notices to Airman not issued by airport personnel indicating that the meteorological equipment was inoperative.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06LA061
- Event ID
- 20060113X00071
- Case number
- CHI06LA061
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-01-05.
- API snapshot SHA-256: 1ef47cae61e025dc7f3105a8bb07a8f2f9c89ae48c459a99ec23bcf74fa1ab19; retrieved 2026-09-22T05:10:11.684Z.