WPR13FA001 · Piper PA-28-180
Piper PA-28-180 · Accident: controlled flight into terrain/object (CFIT) on approach
From Reno-Stead Airport (RTS) to Henderson Executive Airport (HND)
Event
- NTSB case
- WPR13FA001
- 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
- Visual Meteorological Cond
Piper PA-28-180
- 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
- N7895W
- Operator
- Harris Bernard J JR · private individual
- Onboard fatalities
- Unknown
- Route
- From Reno-Stead Airport (RTS), Reno-Stead, NVTo Henderson Executive Airport (HND), Henderson Exec, NV
- 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
- 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
- Substantial
Cause areas
- Personnel issues › Experience/knowledge
- 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 pilot reported that a temporary flight restriction (TFR) was in effect for his intended destination airport and that he was unclear on whether the TFR would prevent him from landing at that airport. The TFR stated that transit operations were allowed only if a discrete code was assigned by air traffic control (ATC) before the airplane’s departure. The pilot mistakenly thought he could pick up the discrete code while airborne. Because the pilot was unable to contact ATC at his intended destination during the flight and the airplane was running low on fuel, he diverted to an alternate airport. At the alternate airport, the pilot initiated a straight-in approach to the runway in darkness, over flat, featureless terrain; the pilot reported that the only airport lighting he saw was the airport beacon. During the approach, the airplane struck high tension power lines about 1 mile south of the runway. Further, according to an applicable notice to airmen, the airport that the pilot diverted to was closed when the accident occurred. The pilot most likely flew a lower than desired approach altitude due to the night time conditions and featureless terrain. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane or engine that would have precluded normal operation.
Probable cause
The pilot’s inadequate flight planning, subsequent loss of situational awareness, and failure to maintain clearance from the power lines during a dark night approach to a closed, unlit runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13FA001
- Event ID
- 20121003X15535
- Case number
- WPR13FA001
- 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 2012-10-03.
- API snapshot SHA-256: 5bdf69eefb8ccfef9f7539d7cb471a3760b19ec75c3aa8f3a59e0689391da191; retrieved 2026-09-15T20:04:54.792Z.