FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10FA125 · Piper PA 46-350P

21 Feb 2010 · Belleville, IL, United States

Piper PA 46-350P · Accident: loss of control in flight on approach

From Vero Beach Regional Airport (VRB) to St Louis Downtown Airport (CPS)

Report a problem

Event

NTSB case
CEN10FA125
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
2 · 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 46-350P

Aircraft type
Piper PA-46
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
N350WF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Vero Beach Regional Airport (VRB), Vero Beach, FLTo St Louis Downtown Airport (CPS), Cahokia, IL
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
Defining eventThe 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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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 was on an instrument flight in night instrument meteorological conditions approaching the destination airport. The pilot contacted the approach control facility by radio and was subsequently cleared for an instrument landing system (ILS) approach to the destination airport. During the approach, the air traffic approach controller advised the pilot twice that the airplane was to the right of the approach course. The controller suggested a left turn of 5 to 7 degrees to the pilot. Once the airplane was back on the inbound course, the approach controller instructed the pilot to contact a tower controller. The pilot never contacted the tower controller, but later reestablished contact with the approach controller, who provided radar vectors for a second attempt at the ILS approach. During the second approach, the controller again advised the pilot that the airplane was to the right of the approach course and provided the pilot a low altitude alert. The airplane then started a climb and a turn back toward the inbound course. The controller advised the pilot that the airplane would intercept the inbound course at the locator outer marker (LOM) for the approach and asked if the pilot would like to abort the approach and try again. The pilot declined and responded that he would continue the approach. No further transmissions were received from the pilot. The airplane impacted a building about 0.4 nautical miles from the LOM. The building and airplane were almost completely consumed by the postimpact fire. A postaccident examination revealed no evidence of mechanical malfunction or failure. The airplane's turning ground track and the challenging visibility conditions were conducive to the onset of pilot spatial disorientation.

Probable cause

The pilot’s spatial disorientation and subsequent failure to maintain airplane control during the instrument approach.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10FA125
Event ID
20100223X51349
Case number
CEN10FA125
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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 2010-02-22.
  • API snapshot SHA-256: d8f8ad7e080ea40e0dda12ece6f00fe5e08a978ff7024715e6c8e9c904c83fcb; retrieved 2026-09-13T20:39:54.997Z.