NYC04FA092 · Piper PA-32R-301
Piper PA-32R-301 · Accident: in flight encounter with weather en route
From Darlington County Airport (UDG) to Blue Grass Airport (LEX)
Event
- NTSB case
- NYC04FA092
- 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
- 6 · 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-301
- 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
- N8173U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Darlington County Airport (UDG), Darlington, SCTo Blue Grass Airport (LEX), Lexington, KY
- 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
- En route · cruise
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › Clearance, not maintained
- Pilot in command › Planning/decision, improper
- Pilot in command › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Prior to departing on a night visual flight rules flight, the non-instrument rated pilot telephoned a flight service station and received a standard weather briefing. The briefing included information about cloud cover along portions of the route. Specifically, the cloud cover was described as solid broken to overcast with bases between 3,000 to 4,000 feet msl, and tops at 6,000 feet. The flight proceeded uneventfully through the Tri-Cities Regional Airport (TRI) airspace, before it impact terrain, about 40 miles northwest of TRI. At the time of the accident, visual meteorological conditions prevailed at TRI. However, snowfall was reported in the mountainous area near the accident site. The wreckage was located at an elevation of 3,050 feet. Review of radar data revealed that the airplane was cruising in a northwesterly direction, at 4,500 feet msl. The last recorded radar return was approximately 6 miles southeast of the accident site.
Probable cause
The pilot's improper decision to continue VFR flight into IMC conditions and his failure to maintain terrain clearance, which resulted in controlled flight into terrain. Factors were night, snow and a low ceiling.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC04FA092
- Event ID
- 20040329X00383
- Case number
- NYC04FA092
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-03-22.
- API snapshot SHA-256: c46843b0d99ab97461f65f1d966ee9d1ebdb07d44a0e5743e39d8a77c0526e0f; retrieved 2026-09-20T18:31:11.332Z.