IAD01LA028 · Piper 34-200T
Piper 34-200T · Accident: in flight collision with terrain/water on approach
From Greenbrier Valley Airport (LWB) to Mercer County Airport (BLF)
Event
- NTSB case
- IAD01LA028
- 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
- 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
- Instrument Meteorological Cond
Piper 34-200T
- Aircraft type
- Piper 34
- 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
- N99ED
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Greenbrier Valley Airport (LWB), Lewisburg, WVTo Mercer County Airport (BLF), Bluefield, WV
- 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 · IFR final approach
- 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, incorrect
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot attempted two ILS approaches to the airport, and then was contacted by a lineman informing him that the pilot-controlled runway lights were on the low setting, and he would increase their intensity. The pilot then flew a third approach, and while looking for the lights at the decision height, the airplane impacted trees and came to rest on the ground. The pilot reported no mechanical deficiencies with the airplane, and stated that he may have been concentrating on "looking for the lights," while on the approach and not monitoring his altitude. The weather reported at 1952, included a visibility of 1/4 mile with fog, few clouds at 100 feet, ceiling 800 feet overcast, temperature 39 degrees Fahrenheit, dew point 37 degrees Fahrenheit, and altimeter setting 29.78 inches of mercury. The altimeter setting noted in the airplane after the accident was 29.97. A review of the FAA ILS RWY 23 approach chart for the airport indicated that the decision height for the approach was 300 feet, and the minimum landing visibility was 1 mile. According to the Aeronautical Information Manual (AIM), Section 7-2-3 ALTIMETER ERRORS, "If you do not reset your altimeter when flying from an area of high pressure into an area of low pressure, your aircraft will be closer to the surface than your altimeter indicates. An inch error in the altimeter setting equals 1,000 feet of altitude."
Probable cause
The pilot's failure to enter the correct altimeter setting, which resulted in continued flight below the decision height and a subsequent collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD01LA028
- Event ID
- 20010201X00379
- Case number
- IAD01LA028
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2001-01-20.
- API snapshot SHA-256: c89d1f7a7d6622ab9b4710e03b6843752c825af762bd807ca471acf7a332e89a; retrieved 2026-09-22T12:13:01.988Z.