FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD02FA043 · Piper PA-34-200T

12 Apr 2002 · Oxford, CT, United States

Piper PA-34-200T · Accident: in flight collision with object on approach

From Grand Strand Airport (CRE) to Waterbury Oxford Airport (OXC)

Report a problem

Event

NTSB case
IAD02FA043
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
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
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
N82284
Operator
William M. Mucciaro · private individual
Onboard fatalities
Unknown
Route
From Grand Strand Airport (CRE), GRAND STRAND, SCTo Waterbury Oxford Airport (OXC), Oxford, CT
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
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
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 › IFR procedure, not followed

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

NTSB narrative

After obtaining weather information, the pilot departed on a long cross country flight at night in instrument meteorological conditions. Approximately 2 hours after departure, the pilot was vectored by air traffic control (ATC) to intercept the localizer for the ILS RWY 36 approach at his destination airport. The pilot acknowledged that he had intercepted the localizer, and was cleared for the approach. Subsequently, ATC terminated radar services and approved a change in radio frequency. The pilot acknowledged the instructions, and there were no further communications with him. Data extracted from a handheld GPS unit revealed that during the last 4 minutes of the flight, the airplane made a series of left and right hand turns in the vicinity of the localizer course as it descended towards the airport. However, it was never established on the localizer course. The last recorded position calculated by the GPS occurred at 2118, was at an altitude of 779 feet msl, about 2,000 feet southeast of runway 36. The published decision altitude for the approach was 972 feet msl. A witness said that the airplane flew very low over her home, and sounded like "a motorcycle going full throttle...at a steady constant rate." Another witness said that the airplane flew over his home about 40-50 feet above the trees with the engines "running correctly." He then observed the airplane's landing lights illuminate the tree tops, then the woods, before it collided with terrain. Weather at the time of the accident included wind from 200 degrees at 6 knots gusting to 15 knots, visibility 2 statute miles, ceiling 300 feet overcast, temperature 52 degrees F, and dewpoint 51 degrees F.

Probable cause

The pilot's failure to follow the published instrument approach procedure. Factors were the night and low ceiling conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD02FA043
Event ID
20020501X00600
Case number
IAD02FA043
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 2002-04-13.
  • API snapshot SHA-256: e7f50f8650c2f2d6cf287832f19bedc52c5c9c344c7c2d85a025cb259a19a016; retrieved 2026-09-20T20:02:59.598Z.