FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC04FA170 · Piper PA-32R-301T

18 Jul 2004 · Wheeling, WV, United States

Piper PA-32R-301T · Accident: in flight encounter with weather during landing

From Central Illinois Regional Airport at Bloomington-Normal (BMI) to Wheeling Ohio County Airport (HLG)

Report a problem

Event

NTSB case
NYC04FA170
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
5 · 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 PA-32R-301T

Aircraft type
Piper PA-32
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
N7710M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Central Illinois Regional Airport at Bloomington-Normal (BMI), Bloomington, ILTo Wheeling Ohio County Airport (HLG), Wheeling, 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
Landing
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 encounter with weather
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)
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

  • Pilot in command › Altitude/clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While executing an ILS approach in night instrument meteorological conditions, the approach controller instructed the pilot that radar services were terminated, and to switch to the advisory frequency. The pilot acknowledged the instruction, and no further transmissions were received from the airplane. Review of radar data revealed that the airplane intercepted the final approach course for the runway 3 localizer, where it began a gradual descent. About 4 minutes prior to the accident, the airplane was recorded on the localizer course, at a ground speed of 115 knots; however, radar coverage was subsequently lost. The airplane impacted a wooded area about 1/2 mile west of the runway, approximately abeam the 500-foot markers painted on the runway surface. The wreckage path was oriented approximately 90 degrees left of the inbound approach heading. A postcrash fire consumed the main wreckage. The weather reported at the airport, about 7 minutes prior to the accident, included 2-1/2 statute miles of visibility; mist; few clouds at 200 feet agl, and an overcast cloud layer at 1,800 feet agl. The weather reported at the airport, about 1 minute after the accident, included 3/4 statute miles of visibility; mist; scattered clouds at 200 and 500 feet agl, an overcast cloud layer at 1,800 feet agl. Review of the instrument approach procedure revealed that the minimums for the straight in approach were 3/4 statute miles of visibility, and a decision altitude of 250 feet agl. The missed approach procedure was, climb to 3,000 feet, direct to a VOR located about 6.7 miles northeast of the airport, and hold.

Probable cause

The pilot's failure to maintain terrain clearance while executing an instrument approach. A factor was the night instrument meteorological conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC04FA170
Event ID
20040729X01101
Case number
NYC04FA170
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 2004-07-19.
  • API snapshot SHA-256: 9e5ff2aab958bdf7af504b091d5cbfde24c02679a63ba3bf648c36ae2cfa0270; retrieved 2026-09-20T18:24:42.592Z.