FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MKC90LA085 · Boeing A75N1

14 Apr 1990 · PLEASANT GROVE, AR, United States

Boeing A75N1 · Accident: total loss of engine power (non-mechanical) en route

From Mountain View Wilcox Memorial Field (7M2) to Batesville Regional Airport (BVX)

Report a problem

Event

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

Boeing A75N1

Aircraft type
Boeing A75
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
N1902M
Operator
Paul R. Amos · private individual
Onboard fatalities
Unknown
Route
From Mountain View Wilcox Memorial Field (7M2), Mountain View, ARTo Batesville Regional Airport (BVX), Batesville, AR
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
Total loss of engine power (non-mechanical)
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

  • Fuel system, carburetor › Ice
  • Pilot in command › Carburetor heat, improper use of

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

NTSB narrative

THE PILOT REPORTED THAT DURING FLIGHT, THE ENGINE PROGRESSIVELY LOST POWER. AN EMERGENCY LANDING WAS MADE IN A SMALL CLEARING, BUT THE PILOT WAS UNABLE TO STOP BEFORE THE AIRCRAFT COLLIDED WITH TREES AT THE END OF THE CLEARING. THE PILOT SUFFERED A BROKEN LEG. NO PREIMPACT MECHANICAL PROBLEM WAS FOUND WITH THE AIRCRAFT OR ENGINE. ACCORDING TO ICING PROBABILITY CHARTS, METEORLOGICAL CONDITIONS WERE CONDUCIVE FOR CARBURETOR ICING AT CRUISE POWER.

Probable cause

IMPROPER USE OF CARBURETOR HEAT BY THE PILOT, WHICH RESULTED IN CARBURETOR ICING. THE WEATHER (CARBURETOR ICING CONDITION) WAS A RELATED FACTOR.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MKC90LA085
Event ID
20001212X22990
Case number
MKC90LA085
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: 945817c4f594aa526a481483a7f7c7bd9ee54f8ce3874e8f7561d172b921680e; retrieved 2026-09-21T15:43:27.367Z.