NYC90FA107 · Cessna 182D
Cessna 182D · Accident: in flight encounter with weather en route
From Northumberland County Airport (N79) to H2L · Hazleton, PA
Event
- NTSB case
- NYC90FA107
- 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
- Instrument Meteorological Cond
Cessna 182D
- Aircraft type
- Cessna 182
- 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
- N8757X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Northumberland County Airport (N79), Shamokin, PATo H2L · Hazleton, PA
- 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); 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 › Became lost/disoriented, inadvertent
- Pilot in command › VFR flight into imc, continued
Approximate · Estimated position: the centre of Numidia, PA, the place the record names. Not the accident site.
NTSB narrative
THE AIRPLANE TOOK OFF FROM AN UNCONTROLLED ARPT, ENROUTE TO AN ARPT WITH AN ILS. THE PILOT HAD RECEIVED HIS INSTRUMENT RATING 3 WEEKS PRIOR AND THE AIRPLANE WAS INSTRUMENT EQUIPPED. THERE WAS NO RECORD OF A WEATHER BRIEFING FOR THE PILOT OR A FLIGHT PLAN FOR THE TRIP. RADAR DATA SHOWED A UNIDENTIFIED CODE 1200 AND THEN A PRIMARY TARGET MOVING FIRST IN AN EASTERLY DIRECTION, MANEUVERING, AND THEN HEADED BACK WEST. THE LAST TARGET WAS 7 MILES FROM THE ACCIDENT SITE APPROXIMATELY 3 MINUTES PRIOR TO THE ACCIDENT. THE AIRCRAFT IMPACTED TREES ON A RIDGE LINE HEADING IN A WESTERLY DIRECTION, HEADING TOWARD THE AIRPORT OF DEPARTURE. EYEWITNESSES IN THE AREA REPORTED REDUCED VISIBILITY WITH FOG ON THE MOUNTAIN.
Probable cause
INFLIGHT COLLISION WITH TREES WHILE ATTEMPTING TO MAINTAIN VISUAL REFERENCE WITH THE GROUND IN INSTRUMENT METEOROLOGICAL FLIGHT CONDITIONS. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT'S DECISION TO CONTINUE THE FLIGHT IN DETERIORATING WEATHER CONDITIONS IN AN AREA OF HIGH TERRAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC90FA107
- Event ID
- 20001212X23256
- Case number
- NYC90FA107
- 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: b526c859f1796a273dc9a0f496a8e2529635623cfd5f4ef06503f913dd8bb3b2; retrieved 2026-09-21T02:42:45.941Z.