FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13FA067 · Piper PA-28-180

21 Nov 2012 · Hillsdale, MI, United States

Piper PA-28-180 · Accident: controlled flight into terrain/object (CFIT) on approach

From Warren County Airport/John Lane Field (I68) to Hillsdale Municipal Airport (JYM)

Report a problem

Event

NTSB case
CEN13FA067
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
Unknown
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-28-180

Aircraft type
Piper PA-28
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
N40781
Operator
Clarence J Avery · private individual
Onboard fatalities
Unknown
Route
From Warren County Airport/John Lane Field (I68), Lebanon, OHTo Hillsdale Municipal Airport (JYM), Hillsdale, MI
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
Defining eventThe 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
Controlled flight into terrain/object (CFIT)
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

After a 1.5-hour uneventful night visual flight rules cross-country flight and about 18 miles from the destination airport, the pilot contacted the airport UNICOM and requested that the runway lights be turned on. Subsequently, the airport manager who was monitoring the UNICOM frequency turned on the runway lights. The airplane did not land, and no distress calls from the pilot were reported. The wreckage was found 1.25 miles east of the approach end of the runway. Examination of the wreckage indicated that the airplane struck the trees in a shallow descent. The airport manager and another pilot reported that hazy conditions existed about the time of the accident. No mechanical anomalies were discovered with the airframe or engine.

The pilot only had 16.4 hours of night flight time, and his most recent logged night flight time was about 10 years before the accident flight. Family members stated that the pilot did not like to fly at night. The selected runway's precision approach path indicator (PAPI) system was not functional. An experienced pilot who landed his airplane at the airport shortly before the accident reported that he chose to land on another runway after circling the airport and noting that the PAPI was nonfunctional because it was dark on that side of the airport. Examination of the altimeter at the accident site showed that 30.38 inches of Mercury (inHg) was set in the instrument's Kollsman window; however, the area barometric pressure at the time of the accident was 30.17 inHg. The altimeter was bench tested and found to be functional. The inaccurate Kollsman setting would have shown a higher indicated altitude on the altimeter in relation to the airplane's actual altitude over terrain. Thus, the pilot likely thought that he was flying at a higher altitude if he was relying solely on the altimeter instead of on outside visual references during the approach. The combination of the pilot's lack of night flying time, the nonfunctional PAPI system, and the inaccurate altimeter setting all contributed to the accident.

Probable cause

The pilot's failure to maintain clearance from terrain during a straight-in night visual flight rules approach to land in hazy weather conditions. Contributing to the accident were the pilot's lack of recent night flying experience, the nonfunctional precision approach path indicator system on the selected runway, and the inaccurate Kollsman setting in the altimeter.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13FA067
Event ID
20121121X13305
Case number
CEN13FA067
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 0d9e007cbd8b42885ba0e17c6d2de20c5f2d142a4647aaa16d0bf5ba5c8c2465; retrieved 2026-09-14T15:48:45.807Z.