CEN09FA562 · Piper PA-32R-300
Piper PA-32R-300 · Accident: controlled flight into terrain/object (CFIT) while maneuvering
From Tulsa Riverside Airport (KRVS) to Dallas Love Field (KDAL)
Event
- NTSB case
- CEN09FA562
- 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
- 5 · 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-32R-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
- N1228H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tulsa Riverside Airport (KRVS), Tulsa, OKTo Dallas Love Field (KDAL), Dallas, TX
- 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
- Maneuvering
- 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
- Controlled flight into terrain/object (CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The non-instrument-rated private pilot obtained a standard weather briefing for a cross-country flight and was advised that a visual flight rules (VFR) flight was not recommended. The ceiling was 600 feet overcast with 4 miles visibility. Approximately 4 hours later, the pilot radioed ground control for taxi and a VFR clearance. The controller informed the pilot that the airport was in instrument flight rules (IFR) conditions. The pilot then requested and received an IFR clearance.
The pilot departed and had to be reminded by the local and departure controllers to make several course and altitude changes. The pilot acknowledged the changes but took no action. The pilot was also warned of antennas near his position. Review of radar data revealed the pilot's altitude varied from 1,100 feet mean sea level (msl) to 1,600 feet (msl). The last radar target was at 1,200 feet msl in a left descending turn although the pilot had been instructed to climb to 4,000 feet 2 minutes before the accident. During periods of low visibility, a pilot is particularly vulnerable to spatial disorientation. Further, the pilot's descending turn when he was supposed to be climbing is indicative of spatial disorientation. The airplane then collided with a guy wire on a 600-foot radio transmission tower at a terrain elevation of 860 feet msl.
Postaccident examination of the airframe, flight controls, engine assembly, and accessories revealed no anomalies. The altimeter, transponder, and transponder automatic altitude reporting system test was current. The gyroscopic instruments were destroyed and could not be examined.
Probable cause
The non-instrument-rated pilot’s decision to attempt flight in instrument meteorological conditions, which resulted in spatial disorientation and an in-flight collision with a radio tower guy wire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09FA562
- Event ID
- 20090905X31040
- Case number
- CEN09FA562
- 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: 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: 0cac815b5869888d5f7fda22eec4e55e957dc59dddeed3a356de2a7bbbce8806; retrieved 2026-09-13T20:27:16.114Z.