LAX01FA036 · Piper PA28-200
Air West Flying Club Piper PA28-200 · Accident: loss of control in flight during an uncontrolled descent
From Page Municipal Airport (PGA) to Rocky Mountain Metropolitan Airport (BJC)
Event
- NTSB case
- LAX01FA036
- 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
- 0
- 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 PA28-200
- Aircraft type
- Piper PA28
- 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
- N3032R
- Operator
- Air West Flying Club
- Onboard fatalities
- Unknown
- Route
- From Page Municipal Airport (PGA), Page, AZTo Rocky Mountain Metropolitan Airport (BJC), Broomfield, CO
- 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
- Uncontrolled descent
- 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
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › VFR flight into imc, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A Safety Board staff meteorologist performed a weather analysis for the flight. Airmet's for instrument flight rules, mountain obscuration, turbulence, and icing were valid for all portions of the airplane's flight route. The airplane brokeup in flight. The pilot contacted the FAA Prescott Automated Flight Service Station (AFSS) by telephone from Page, Arizona, at 1306, and requested a forecast for Pueblo, Colorado. The forecast was for winds gusting to 30 knots; showers in the vicinity; scattered clouds at 4,000 agl; broken clouds at 7,000 agl; lowering clouds after 1700; and an increase in occasional rain and snow showers. The pilot was issued an Airmet for icing in Colorado mountain obscuration, and from Phoenix to Denver, turbulence from the surface to 39,000 feet. During the briefing the pilot told the briefer that he was "trapped in Page, trying to get back the Denver; when does it look like the system is going to clear out a little, do you have any information on that?" At 1420, the pilot contacted the Prescott AFSS by radio over Kayenta, Arizona, about 60 miles west of the accident site. He requested, and was given, the current weather conditions at Grand Junction and Farmington, New Mexico. He requested three other locations in Colorado; all were marginal for visual flight. At 1425, the pilot told the briefer "we'll be heading the southern route." The pilot did not file a flight plan. On November 6, at 1155, the Air Force Rescue Coordination Center (AFRCC) provided notification of an emergency crash locator beacon signal. Subsequently the wreckage was located at 1845, in the Carrizo Mountains, at an elevation of about 8,610 feet msl, approximately 51 nautical miles on the 260-degree radial from the Farmington VOR navigational facility. According to accident flight reconstruction information, the airplane departed Broomfield, Colorado, on November 3, and was returning the day of the accident. The pilot had not told the flying club operator of his intended destination, only that he would be back with the plane on the 5th about 1800. The airplane was refueled at North Las Vegas, on November 4, and at Page on November 5. According to fuel service witness information at Page, the airplane made a fuel stop and departed. The fuel invoice was paid at 1338. According to the flying club, it is their written and member signed policy to require all members to file flight plans for flights over 50 nautical miles or more, and all cross-country flight destinations are to be given to the operator. Information recovered from a notepad found in the wreckage documented a flight route from Broomfield (Jeffco), Monarch Pass, Blue Mesa, Dove Creek, Page, and Las Vegas, for a total distance of 545 miles.
Probable cause
In-flight loss of control resulting in airframe structural failure. Contributing to the accident was the pilot's inadvertant visual flight into instrument meteorological conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01FA036
- Event ID
- 20001212X22297
- Case number
- LAX01FA036
- 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: 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: 1f52229d8870e1e56c48144e72632c3680d7fed04d41c2185506bd4c1f989ae1; retrieved 2026-09-20T20:47:45.002Z.