19901018052599I

Incident

FAA incident report · Cessna 172N · Bluefield, WV · October 18, 1990

Date: October 18, 1990 · 22:38 local
Place: Bluefield, WV
Airport: Mercer County
Phase of flight: Fcd/Prec Ldg From Cruise
Operating rules: General operating rules (Part 91)
Aircraft: N9400E
Reported as: Cessna 172N
People aboard: 1
Fatal injuries: 0
Pilot’s flight hours: 330 total200 in this make and model60 in the last 90 days

N9400ERegistered now · Cessna 172NS/N 17272249 · Built 1979 Airframe modelCessna 172N Engine modelLycoming 0-320 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

Airspeed indicator failed. In turbulence. Declared emergency. Had forgotten to turn on pitot heat.

As the FAA filed it

AIRSPEED INDICATOR FAILED. IN TURBULENCE. DECLARED EMERGENCY. HAD FORGOTTEN TO TURN ON PITOT HEAT.

Other reports on N9400E · 2

Matched to the same aircraft by N-number and date.

Accident 20140806015069ALanding: Rollout · Valkaria, FLStudent pilot (sp) on first-ever solo flight heard a loud "bang" from the engine, accompanied by substantial engine vibration and sudden partial loss of power to 1900 RPM during climb-out from runway 28 at Valkaria Airport, FL (X59). Sp elected to turn back…Aug 6, 2014 · Substantial damage Incident 19800720062089ILevel Off Touchdown · Biloxi, MSHard landing damaged firewall and nose wheel.Jul 20, 1980 · Minor damage