NYC97FA004 · Beech F33A
Beech F33A · Accident: in flight encounter with weather en route
From Allegheny County Airport (AGC) to Altoona Blair County Airport (AOO)
Event
- NTSB case
- NYC97FA004
- 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
- 2 · 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
Beech F33A
- Aircraft type
- Beechcraft 33
- 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
- N2154L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Allegheny County Airport (AGC), Pittsburgh, PATo Altoona Blair County Airport (AOO), Altoona, 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)
- 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
- 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
Before departure, the pilot was advised by Flight Service Station personnel that VFR flight was not recommended due to low clouds across the mountain ridges along the route of flight. The pilot then elected to depart on a night, VFR, cross-country flight. The airplane was reported missing, and it was located in mountainous terrain along the intended route. The crash site was near the top of a 2,100 foot mountain, at an elevation of about 2,000 feet msl. Cloud layers were reported between 1,500 and 2,500 feet msl at surrounding airports. Witnesses reported that the weather was rainy and foggy at the accident site. Examination of the wreckage did not reveal any evidence of a preimpact malfunction.
Probable cause
continued VFR flight by the pilot into instrument meteorological conditions, and his failure to maintain altitude and/or clearance from high terrain. Factors relating to the accident were: darkness, low ceiling, fog, and high (mountainous) terrain along the route.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC97FA004
- Event ID
- 20001208X06956
- Case number
- NYC97FA004
- 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: 21022c8cf4db0f38b15bcb872945d9197e57509e71c179638219f8627f589114; retrieved 2026-09-20T23:10:32.323Z.