LAX08FA001 · Piper PA-28R-200
Piper PA-28R-200 · Accident: loss of control in flight en route
From Skypark Airport (BTF) to Colorado City Municipal Airport (AZC)
Event
- NTSB case
- LAX08FA001
- 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
- Visual Meteorological Cond
Piper PA-28R-200
- 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
- N3971X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Skypark Airport (BTF), Bountiful, UTTo Colorado City Municipal Airport (AZC), Colorado City, AZ
- 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
- En route · cruise
- 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
- 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
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Spatial disorientation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The non-instrument-rated private pilot's departure had been delayed, and he was in a hurry to fly home. The pilot elected to fly over mountainous terrain in dark, nighttime conditions. Recorded radar data shows that after cruising for nearly 2 hours, the airplane initially entered a slow descent from 12,600 to 11,100 feet. Thereafter, the radar track shows the airplane commencing a clockwise turn while continuing to descend. While reversing course, the pilot became spatially disoriented, and the airplane rapidly descended, as evidenced by its sudden disappearance from radar. During the descent the airplane broke apart. Wreckage was found on a 6,400-foot (mean sea level) mountain and was scattered over a 950 by 350 foot oval-shaped area. The major components that separated were the horizontal stabilator, the vertical tail surfaces, and the 6-foot-long outboard span of both wings. The propeller blades exhibited signatures consistent with the absorption of rotational energy during ground impact. No preimpact anomalies were found during the wreckage examination and all fractures were overload in character. The descending flight profile, followed by the course reversal away from the pilot's destination, was consistent with a spiral maneuver. The structural breakup resulted from aerodynamic forces induced by the pilot's recovery attempts that exceeded the airframe's strength.
Probable cause
The pilot's failure to maintain aircraft control while in cruise flight due to spatial disorientation. Contributing to the accident were the dark conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08FA001
- Event ID
- 20071105X01726
- Case number
- LAX08FA001
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-10-27.
- API snapshot SHA-256: 6c0d254440bb71a6b2ef2199e5a6be6edba6dbd6167c4e772ae45191c6e67ab4; retrieved 2026-09-20T16:10:07.806Z.