FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC96FA035 · Cessna 152

3 Dec 1995 · RUSH TOWNSHIP, PA, United States

Cessna 152 · Accident: in flight encounter with weather while maneuvering

From Shenandoah Valley Regional Airport (SHD) to DuBois Regional Airport (DUJ)

Report a problem

Event

NTSB case
NYC96FA035
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 152

Aircraft type
Cessna 152
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
N67369
Operator
Unknown
Onboard fatalities
Unknown
Route
From Shenandoah Valley Regional Airport (SHD), Weyers Cave, VATo DuBois Regional Airport (DUJ), DU BOIS, 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
Maneuvering
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
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 › Flight into adverse weather, continued

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot had transmitted a 'MAYDAY', and radar and radio communications were established with the pilot by the Altoona Flight Service Station (FSS). The pilot reported '...I'm lost and...give me vectors to an airport.' He was given his location and asked to verify his altitude. He responded that he was at 3,300 feet, but the recorded radar data showed that the altitude was actually 3,000 feet. The controller asked the pilot if he was IFR qualified and was the aircraft equipped for IFR flight. The pilot answered he was 'not IFR rated,' but that the airplane was equipped for IFR flight. The pilot further informed the controller that he had half tanks of fuel remaining in both fuel tanks. The controller asked the pilot if he was in 'good' VFR flight condition and the pilot answered 'negative sir in and out.' Radar showed that the airplane was at 2,600 feet, and the controller advised the pilot that the emergency safe altitude was 2,500 feet. The pilot was also advised that the closest airport to his current position with acceptable ceilings was 20 to 25 miles northeast. The pilot was asked if he could maintain VFR conditions at 3,000 feet. He never answered. An ELT signal was heard and communications was never reestablished. The last two radar returns showed that the airplane was heading in a southerly direction, at altitudes of 2,600 and 2,700 feet. Searchers located the airplane wreckage in rising mountainous terrain the next morning at an elevation of 2,100 feet. The top of the mountain that the airplane impacted was 2,600 feet. Witnesses had heard a low flying aircraft in the area just before the accident, but couldn't see the airplane due to the heavy clouds and fog.

Probable cause

the pilot's continued flight into adverse weather conditions which resulted in becoming lost and disorientated and subsequent impact with rising terrain. Factors in this accident were fog and a dark night.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC96FA035
Event ID
20001207X05065
Case number
NYC96FA035
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: dbad9b6182341e4a4b3b407c5495cb037499c206610f329fd6ef9e150f27e47d; retrieved 2026-09-20T23:30:37.529Z.