FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX92LA044 · Cessna 170B

11 Nov 1991 · LAKE HAVASU, AZ, United States

Cessna 170B · Accident: in flight collision with terrain/water on approach

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

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
LAX92LA044
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

Cessna 170B

Aircraft type
Cessna 170
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
N8172A
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
Approach · VFR pattern base
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 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 › Altimeter setting, not obtained
  • Pilot in command › Notams, inadequate
  • Pilot in command › Preflight planning/preparation, inadequate

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

NTSB narrative

DURING A NIGHT CROSS COUNTRY FLIGHT TO A NEW AND UNFAMILIAR AIRPORT, THE PILOT UNSUCCESSFULLY ATTEMPTED TO ESTABLISH FLIGHT FOLLOWING AND OBTAIN CURRENT ALTIMENTER SETTINGS. HE FLEW OVER THE AIRPORT AND ENTERED A TRAFFIC PATTERN. DURING THE TRUN FROM BASE TO FINAL APPROACH, WITH THE RUNWAY LIGHTS IN SIGHT, THE AIRPLANE COLLIDED WITH THE TERRAIN ONE AND ONE QUARTER MILES SHORT OF THE RUNWAY. THE PILOT DID NOT TURN ON THE AIRCRAFT LANDING LIGHT. FAA RECORDS INDICATE THE PILOT DID NOT RECEIVE A PREFLIGHT BRIEFING. THE VFR AERONAUTICAL CHART DID NOT SHOW THE NEW AIRPORT. THE OLD AIRPORT ELEVATION IS 483 FT MSL, AND THE NEW AIRPORT IS 780 FT MSL. THE CHART DEPICTING THE NEW AIRPORT BECAME EFFECTIVE 3 DAYS AFTER THE ACCIDENT. FAA PERSONNEL REPORTED THAT A NOTAM IN EFFECT CONTAINED INFORMATION PERTINENT TO THE NEW AIRPORT. AFTER THE ACCIDENT, THE PILOT REPORTED THAT HIS ALTIMETER INDICATED 1,000 FT MSL.

Probable cause

THE PILOT'S; 1) INADEQUATE PREFLIGHT PREPARATION, 2) FAILURE TO OBTAIN CURRENT NOTAM INFORMATION, AND 3) FAILURE TO OBTAIN A CURRENT ALTIMETER SETTING. FACTORS IN THE ACCIDENT WERE THE DARK NIGHT CONDITION AND THE PILOT ELECTION NOT TO USE THE LANDING LIGHT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX92LA044
Event ID
20001212X18474
Case number
LAX92LA044
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1991-11-12.
  • API snapshot SHA-256: e016e12fd4fcdf52e6eeba32cbafddfc0bc6e25f2d51a0c538623205038e0be5; retrieved 2026-09-23T03:32:44.603Z.