FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

P.M. Air Piper PA-31-350 accident

21 Sept 1990 · Flagstaff, AZ, United States

Piper PA-31-350 · Accident: in flight encounter with weather on approach

From Phoenix Sky Harbor International Airport (PHX) to an unrecorded destination

Report a problem

Event

NTSB case
LAX90FA331
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
1 · 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
Charter & commuter
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-31-350

Aircraft type
Piper PA-31
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
N3558
Operator
P.M. Air
Onboard fatalities
Unknown
Route
From Phoenix Sky Harbor International Airport (PHX), Phoenix, AZTo not recorded
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 135: Air Taxi & Commuter
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
Approach
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
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 › Proper altitude, not maintained
  • Pilot in command › VFR flight into imc, inadvertent

Approximate · Estimated position: the centre of Flagstaff, AZ, the place the record names. Not the accident site.

NTSB narrative

THE ACFT WAS ON A NIGHT FLT FM PHOENIX TO FLAGSTAFF, AZ, TO DELIVER CARGO IN ACCORDANCE WITH AN AIR TAXI DELIVERY SCHEDULE. BFR REACHING FLAGSTAFF, THE PLT CANCELED HIS IFR CLNC & PROCEEDED VFR. HE ENCTRD LOWERING CIGS & RW. DRG THE APCH, HE EXTENDED THE LNDG GEAR & PARTIALLY EXTENDED THE WING FLAPS. SUBSEQUENTLY, THE ACFT HIT TREES & CRASHED IN AN UNPOPULATED AREA ABT 2.5 MI SSE OF THE ARPT AT AN ELEV OF ABT 6800 FT; ARPT ELEV WAS 7011 FT. INITIAL IMPACT OCCURRED WHILE THE ACFT WAS IN A RIGHT 20 DEG BANK (TOWARD RWY 3). WX DATA AT THE COMPANY DISPATCH WAS NOT CURRENT & DID NOT DEPICT THE ADVERSE LOCAL CONDS NEAR THE DESTN ARPT.

Probable cause

VFR FLIGHT BY THE PILOT INTO INSTRUMENT METEOROLOGICAL CONDITIONS (IMC), AND HIS FAILURE TO MAINTAIN PROPER ALTITUDE DURING THE APPROACH TO LAND. FACTORS RELATED TO THE ACCIDENT WERE: DARKNESS, THE ADVERSE WEATHER CONDITIONS, AND FAILURE OF COMPANY/OPERATOR/MANAGEMENT PERSONNEL TO PROVIDE CURRENT WEATHER.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX90FA331
Event ID
20001212X24295
Case number
LAX90FA331
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: ee5fe5444ed6c05061f20dd0ffeecd2b14ceab84331fb8ed1f3e153a276f2449; retrieved 2026-09-18T14:05:30.065Z.