LAX07FA123 · Cessna 172N
Cessna 172N · Accident: loss of control in flight while maneuvering
From Page Municipal Airport (PGA) to North Las Vegas Airport (VGT)
Event
- NTSB case
- LAX07FA123
- 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
Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N6267D
- Operator
- Robert W. Patterson · private individual
- Onboard fatalities
- Unknown
- Route
- From Page Municipal Airport (PGA), Page, AZTo North Las Vegas Airport (VGT), North Las Vegas, 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
- Maneuvering · turn to reverse direction
- 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
- Stall/spin
- 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 › Airspeed(vso), not maintained
- Pilot in command › Altitude/clearance, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The two private pilots had flown to Colorado to visit relatives and the accident occurred during their return flight to their home airport. Both pilots were current in the airplane. However, the pilot in the left seat was more experienced, being certificated in 1986 and having 220 total flight hours, of which 111 were in cross-country flying. The pilot in the right seat was certificated in 2006. His total flying and cross-country experience was, respectively, 79 and 22 hours. Prior to taking off from the intermediate fuel stop (at an elevation 4,316 feet mean sea level), the airplane's fuel tanks were topped off. This action increased the airplane's gross weight to within 100 pounds of its certificated maximum weight. Thereafter, the pilots departed under a clear sky with at least 10 miles visibility on a westerly course toward Nevada. The pilots entered an area of rapidly rising terrain, which would have been in clear view as they approached the area. The flying pilot failed to initiate a climb in sufficient time to avoid the mountainside in a box-like canyon. Based on a review of the ground scars and impact signatures in the wreckage, as the pilot attempted to reverse course in the canyon, the airplane appeared to have stalled and impacted a rocky outcrop while in a nose down attitude. The collision occurred about 250 feet below the rim of the canyon wall, at an elevation of 5,670 feet msl. Post accident inspection of the airframe and engine found no evidence of a mechanical failure or malfunction.
Probable cause
The pilot's failure to maintain an adequate terrain clearance altitude, and, his failure to maintain an adequate airspeed while maneuvering to reverse course in a box canyon. Contributing to the accident were the rising terrain and the box canyon.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07FA123
- Event ID
- 20070423X00447
- Case number
- LAX07FA123
- 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, coordinates. 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: 1cf43155c8e5ef05e4b90bb3efb27c776229272d096a6dd94885657a1fce2566; retrieved 2026-09-20T16:44:56.315Z.