NYC01FA123 · Cessna 150A
Cessna 150A · Accident: in flight collision with object while maneuvering
From John Murtha Johnstown Cambria County Airport (JST) to John Murtha Johnstown Cambria County Airport (JST)
Event
- NTSB case
- NYC01FA123
- 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
- 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
- Visual Meteorological Cond
Cessna 150A
- Aircraft type
- Cessna 150
- 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
- N7064X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From John Murtha Johnstown Cambria County Airport (JST), Johnstown, PATo John Murtha Johnstown Cambria County Airport (JST)
- 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 collision with object
- 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
- Wire, transmission (marked)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
GPS data revealed that the accident airplane departed on runway 23 at 0737 and made a right turn towards the north. It flew in a northerly direction until 0742, then flew northeasterly until the final data plot at 0743:16. A shift supervisor at the local electric company reported a power interruption at 0743, and the wreckage was found underneath transmission lines. The lines were approximately 300 feet above the ground, and scrape marks were observed on both the wreckage and the lines. Witnesses near the accident site reported a low-flying airplane about the time of the accident. Additionally, a local flight instructor stated that the accident site was located along a route commonly flown by the pilot, and he previously counseled the pilot about low flying. Examination of the wreckage did not reveal any pre-impact mechanical malfunctions.
Probable cause
The pilot's inadequate visual lookout while manuevering at low level. A factor was the pilot's improper decision to conduct low-level flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01FA123
- Event ID
- 20010518X00953
- Case number
- NYC01FA123
- 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, coordinates. 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: a4dedef7bfb7efa359304f0ea6505ebbd14ba410f4e62afb16575ff454ec2cfd; retrieved 2026-09-20T20:33:19.270Z.