FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC84FA135 · Piper PA-34-200T

6 Apr 1984 · Johnstown, PA, United States

Piper PA-34-200T · Accident: in flight collision with terrain/water during takeoff

From John Murtha Johnstown Cambria County Airport (JST) to Abraham Lincoln Capital Airport (SPI)

Report a problem

Event

NTSB case
NYC84FA135
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

Piper PA-34-200T

Aircraft type
Piper PA-34
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
N33569
Operator
Unknown
Onboard fatalities
Unknown
Route
From John Murtha Johnstown Cambria County Airport (JST), Johnstown, PATo Abraham Lincoln Capital Airport (SPI), Springfield, IL
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
Takeoff
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 terrain/water
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 › Aircraft preflight, inadequate
  • Wing › Ice

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

NTSB narrative

THE ACFT TOOK OFF WITH A CENTER OF GRAVITY BET 95.45 & 95.71 INCHES AFT OF THE DATUM & APRX 98 LBS BELOW THE MAX ALLOWABLE GROSS WEIGHT. THE MAX AFT CG LIMIT FOR ALL WEIGHTS WAS 94.6 INCHES. WX AT THE APRX TIME OF THE ACCIDENT WAS 400 FT CEILING, LIGHT SNOWSHOWERS, 4 MILES VISIBILITY WITH FOG, TEMP 29F, DEW POINT 29F. A SIGMET FOR MOD TO SEVERE ICING IN CLOUDS WAS ALSO IN EFFECT. THE ACFT IMPACTED IN A 30 TO 40 DEG LEFT BANK. IMPACT OCCURRED APRX 1800 FT FROM THE DEPARTURE END OF THE RWY. THERE WAS NO EVIDENCE OF INFLIGHT MECHANICAL MALFUNCTIONS OF THE POWERPLANTS. ALTHOUGH THEACFT ARRIVED AT JOHNSTOWN WITH ICE ON THE WINGS AND TAIL, THE PLT RECEIVED A FULL WX BRIEFING AND WAS AWARE OF THE ICINGCONDITIONS PRIOR TO HIS LAST TAKEOFF. THERE WAS EVIDENCE THAT THE PLT DID NOT DEICE THE ACFT'S WINGS AND TAIL PRIOR THE ACCIDENT FLT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC84FA135
Event ID
20001214X39377
Case number
NYC84FA135
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 1984-04-07.
  • API snapshot SHA-256: 7ad9969d2ce1a7efdac36dee6ea0515da6ad62d20f5c7a4e94f5fa80621dd3d5; retrieved 2026-09-21T05:35:16.232Z.