CHI82FA024 · Piper PA-28-140
Piper PA-28-140 · Accident: undershoot on approach
From Jefferson County Airpark (2G2) to Harry Clever Field (PHD)
Event
- NTSB case
- CHI82FA024
- 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
- 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-28-140
- 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
- N207CB
- Operator
- John Byard
- Onboard fatalities
- Unknown
- Route
- From Jefferson County Airpark (2G2), Steubenville, OHTo Harry Clever Field (PHD), New Philadelphia, OH
- 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 final
- 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
- Undershoot
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s); Fuel starvation
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Fluid, fuel › Starvation
- Fuel system › Previous damage
- Fuel system, strainer › Disconnected
- Pilot in command › Altitude, misjudged
- Pilot in command › Distance, misjudged
- Pilot in command › Proper glidepath, below
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE ON FINAL APPROACH THE AIRCRAFT CONTACTED A TREE ABOUT 70 FEET HIGH AND 920 FEET FROM THE DISPLACED THRESHOLD TO RUNWAY 14. THE PILOT THEN ELECTED TO INITIATE A GO-AROUND AND CLIMBED STRAIGHT AHEAD. AFTER COMPLETING A 180 DEGREE TURN TO DOWNWIND THE ENGINE LOST POWER AND THE PILOT ATTEMPTED TO MAKE A FORCED LANDING OFF THE AIRPORT. THE AIRCRAFT IMPACTED A 40 FOOT TALL TREE NEAR BEAVER DAM CREEK AND CAME TO REST NEXT TO A LARGE OAK TREE. DURING REMOVAL OF THE LOWER ENGINE COWL THE GASCOLATOR(CUP) FELL TO THE GROUND. EXAMINATION OF THE HOLE IN THE COWLING NORMALLY USED FOR ACCESS TO THE GASCOLATOR SHOWED EVIDENCE OF BEING STRUCK BY ONE OR MORE TREE BRANCHES. THE WIND WAS GUSTING TO 24 KNOTS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI82FA024
- Event ID
- 20020917X01881
- Case number
- CHI82FA024
- 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: a73e55913457d87e141e2d7df624dd9837b53bd847b7a718c8ff4bfa9bb8014f; retrieved 2026-09-21T08:39:55.369Z.