FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03FA069 · Piper PA-23-250

8 Jan 2003 · Flagstaff, AZ, United States

Piper PA-23-250 · Accident: in flight encounter with weather en route

From 61B · Boulder City, NV to Midland International Air and Space Port (MAF)

Report a problem

Event

NTSB case
LAX03FA069
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
Instrument Meteorological Cond

Piper PA-23-250

Aircraft type
Piper PA-23
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
N135LA
Operator
Unknown
Onboard fatalities
Unknown
Route
From 61B · Boulder City, NVTo Midland International Air and Space Port (MAF), Midland, TX
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
In flight encounter with weather
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 › Altitude, not maintained
  • Pilot in command › Atc clearance, not complied with

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane collided with trees and mountainous terrain after encountering adverse weather conditions, including clouds, rain, and moderate rime icing. The airplane was on a cross-country flight across northern Arizona and was receiving VFR flight advisories from Albuquerque Air Route Traffic Control Center (ARTCC). While en route near Flagstaff at 11,500 feet mean sea level (msl), the pilot advised the controller that he was unable to maintain visual flight due to clouds, rain, and ice, and requested an IFR clearance into Flagstaff. Review of the recorded air-to-ground communications tapes disclosed that the transmission from the airplane was scratchy and of poor quality. The investigation later determined that on the morning of the accident, an underground fiber optic communication line was cut, which disrupted the quality of air-to-ground and ground-to-air communications in northern Arizona, causing broken and garbled services. Landline communications were also affected, which required a nearby Flight Service Station to relay land line messages between the tower and the ARTCC. The controller advised the pilot of rime ice reports at 13,000 feet on his course, and the pilot responded that his altitude was 12,000 feet and he was accumulating some ice. The controller advised the pilot of the airport's location. The pilot's reply was broken and unreadable. The controller asked the pilot if he had the airport in sight, and the pilot responded that no he was in some clouds. The pilot then requested to go to the tower frequency and land, and the controller issued a VFR transponder code and handed the flight off to the tower. About 2 minutes later the pilot reported back to the controller and advised that he was unable to get a visual on the ground and would like to get an IFR clearance into the airport. The controller advised the pilot to climb to 11,000 feet. and enter the published holding pattern southeast of the FLG VOR on the 113-degree radial. The pilot acknowledged the clearance and this was the last communications received from the aircraft. The wreckage was located 10 miles north of the VOR at 8,900 feet msl. Impact signatures and ground scars showed the aircraft collided with mature pine trees in a near wings level attitude while in a shallow descent. A post crash fire destroyed the cockpit, including the navigation radios and related instrumentation. On December 6, 2002, the Flagstaff visual omni range (VOR) navigational aid frequency was changed from 108.2, to 113.85. A partially burned Phoenix sectional chart dated November 1, 2001, was recovered from the wreckage that listed 108.2 as the VOR frequency. No other navigational reference material was recovered from the burned wreckage.

Probable cause

the pilot's failure to comply with his instrument clearance route instruction and to maintain his assigned altitude. A factor in the accident was the poor quality of radio communications due to the severance of underground fiber optic voice and data lines for the ARTCC, which also affected inter and intra facility landline communications.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03FA069
Event ID
20030117X00080
Case number
LAX03FA069
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: 9f21ca38c42769bc79d58044cad108f8367cd55019613e831fa621e3dd22229f; retrieved 2026-09-20T19:31:54.156Z.