WPR24FA002 · Piper PA-28-140
Piper PA-28-140 · Accident: controlled flight into terrain/object (CFIT) during initial climb
From an unrecorded airport to Casper-Natrona County International Airport (CPR)
Event
- NTSB case
- WPR24FA002
- 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
- 4 · 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-140
- 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
- N7153R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Casper-Natrona County International Airport (CPR), Casper, WY
- Aircraft age
- About 57 years (built 1966)
- 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
- Initial climb
- 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)
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- 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 and three family members departed to return to their home airport. The departure was during dark nighttime conditions and into an area with little ambient light for visual reference. A witness statement, confirmed by video evidence, indicated that the pilot did not use the pilot-controlled runway lights and turned off the airplane landing light immediately after takeoff. Review of ADS-B data showed that, while at a low altitude, the airplane began a continuous 180° right turn that was described by the witness as steep and descending. Impact marks indicated that the pilot likely began a climb or held a nose-up attitude before the airplane’s landing gear struck a hill. The airplane continued beyond this first hill for about 540 ft, where it then descended in a nose-low attitude and impacted a second hill. The impacts fatally injured the occupants and substantially damaged the airplane. Before the accident flight, the pilot received a weather briefing that reported visual meteorological conditions for the departure airport, route of flight, and destination airport. The briefing did not include information on moon rise or illumination. A weather study revealed that, at the time of takeoff, the full moon had not risen completely above the horizon. The pilot did not use the functional pilot-controlled runway lights, thus eliminating this light source as a possible visual aid during the departure. Additionally, a local operator stated that their company pilots do not usually depart on the runway used by the accident pilot at night due to the dark conditions and the lack of visual references. The Federal Aviation Administration (FAA) Airplane Flying Handbook advised pilots flying at night that, after becoming airborne, the darkness of night often makes it difficult to note whether the airplane is getting closer to or farther from the surface. The handbook also stated to check flight instruments frequently during takeoff to ensure proper airspeed, attitude, and heading, and to climb to a safe maneuvering altitude before turning. The handbook noted that, when using the landing light at night during takeoff, a pilot should turn it off after the climb is well established. It is likely that the pilot neither had adequate visual references after takeoff nor monitored the airplane’s flight instruments appropriately to detect the airplane’s descent during the continuous 180° crosswind to downwind turn. This likely led to the pilot experiencing spatial disorientation, resulting in controlled flight into terrain. Postaccident examination of the airframe and engine revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. A review of the maintenance logbooks revealed no anomalies.
Probable cause
The pilot’s loss of visual reference to the horizon while departing during dark night, which resulted in the pilot experiencing spatial disorientation and subsequent controlled flight into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24FA002
- Event ID
- 20231002193168
- Case number
- WPR24FA002
- 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, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2023-10-02.
- API snapshot SHA-256: fb0e024094c61a060434aedc869129a5ab466cf7296cb876885c26c9b2cf9216; retrieved 2026-09-15T08:06:27.187Z.