FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC84FA143 · Piper PA-28R-200

18 Apr 1984 · Concord, MA, United States

Haski Aviation Piper PA-28R-200 · Accident: abrupt maneuver on approach

From 8G7 · Zelienople, PA to Laurence G Hanscom Field (BED)

Report a problem

Event

NTSB case
NYC84FA143
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-28R-200

Aircraft type
Piper PA-28
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
N4467X
Onboard fatalities
Unknown
Route
From 8G7 · Zelienople, PATo Laurence G Hanscom Field (BED), Bedford, MA
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
Approach · IFR initial approach
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
Abrupt maneuver
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
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 › Descent, inadvertent
  • Pilot in command › Lack of recent experience in type of aircraft
  • Pilot in command › Proper descent rate, exceeded
  • Pilot in command › Remedial action, attempted
  • Pilot in command › Spatial disorientation

Approximate · Estimated position: the centre of Concord, MA, the place the record names. Not the accident site.

NTSB narrative

THE ACFT CRASHED INTO A HOUSE WHILE ON AN ILS APPROACH TO RWY 11 AT HANSCOM FIELD. SHORTLY BEFORE THE ACFT HAD REACHED THE OUTER MARKER (AND AFTER THE HAND OFF FROM BOSTON APPROACH CONTROL TO HANSCOM TOWER) AN ALTITUDE ALERT ON N4467X WAS RECEIVED BY THE BOSTON APPROACH RADAR CONTROLLER. HE NOTIFIED THE HANSCOM CONTROLLER WHO THEN INFORMED THE PLT OF THE ALERT, TO WHICH THE PLT REPLIED HE WAS AT 1400 FT AND CROSSING THE OUTER MARKER. THIS WAS THE THIRD INSTANCE DURING THE FLT WHERE A DISCREPANCY BETWEEN THE BAROMETRIC ALTIMETER AND THE ENCODING ALTIMETER CAME TO LIGHT. INVESTIGATION ALSO REVEALED THAT THE ACCIDENT OCCURRED AT THE END OF AN 18 HR WORK DAY FOR THE PLT WHO HAD ALSO BEEN ILL WITH THE FLU DURING THE WEEKEND PRECEEDING THE ACCIDENT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC84FA143
Event ID
20001214X39381
Case number
NYC84FA143
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-19.
  • API snapshot SHA-256: cd64c4d74af499cac4c80a743f93a659ea2aff868780e0d7ebf4f2321230ddb6; retrieved 2026-09-21T05:34:23.741Z.