FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX89LA105 · Piper PA-18

8 Feb 1989 · Flagstaff, AZ, United States

Piper PA-18 · Accident: on ground/water collision with terrain/water during landing

From Prescott Regional Airport - Ernest A. Love Field (PRC) to an unrecorded destination

Report a problem

Event

NTSB case
LAX89LA105
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
0 · 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
Visual Meteorological Cond

Piper PA-18

Aircraft type
Piper PA-18
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
N9007S
Operator
Peter Baxter
Onboard fatalities
Unknown
Route
From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, 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 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
Landing · landing roll
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
On ground/water collision with terrain/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Proper alignment, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PLT RPRTD THAT WHEN HE WAS ON FINAL APCH TO LAND, THERE WAS A LEARJET BEHIND HIM ON A 5 MILE FINAL APCH. HE STATED THAT HE MADE A NORMAL LANDING, THEN STEERED LEFT TOWARD THE 'TAXIWAY SIDE' OF THE RWY TO EXPEDITE OFF THE RWY. HOWEVER, AFTER REACHING THE LEFT SIDE, HE WAS UNABLE TO ALIGN THE ACFT BACK ON THE RWY HEADING & ELECTED TO CONTINUE OFF THE RWY, RATHER THAN RISK GROUND LOOPING THE ACFT. AFTER DEPARTING THE RWY, THE ACFT ENTERED SNOW & NOSED OVER. NO MECH MALFUNCTION OR FAILURE WAS RPRTD.

Probable cause

THE PILOT'S FAILURE TO MAINTAIN PROPER RUNWAY ALIGNMENT WHILE EXPEDITING TO EXIT THE RUNWAY. HIS LACK OF EXPERIENCE IN THIS TYPE OF AIRCRAFT, SELF-INDUCED PRESSURE & THE SNOW COVERED TERRAIN WERE CONTRIBUTING FACTORS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX89LA105
Event ID
20001213X27746
Case number
LAX89LA105
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: 01fb0705ec2d262d59bd30eaa15840c03e72fa633fb9befdda0d97b6326fd7d7; retrieved 2026-09-23T07:53:46.964Z.