The U.S. aircraft register, updated daily
Accidents · NTSB CEN15FA087 · Final report

Piper PA-34-200T accident near Port Huron, Michigan, December 24, 2014

On December 24, 2014 at about 5:54 pm local time, a 1977 Piper PA-34-200T, registered N38884, was destroyed in an accident during approach (IFR missed approach) near Port Huron, Michigan (St Clair County International airport). It was a business flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot’s decision to continue flight below the minimum descent altitude without visually acquiring the runway and his delayed and improperly executed missed approach procedure in instrument meteorological conditions.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
December 24, 2014 · about 5:54 pm local time
Place
Port Huron, Michigan · St Clair County International · map
Type
Accident
Injuries
1 person was killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA-34-200T, built 1977 · all PA-34-200Ts on the register
Registration
N38884 · no longer on the register · serial 34-7770352
Damage
Destroyed
Flight
Business flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The private pilot was conducting a business flight. He had obtained weather briefings on the day before and the day of the flight, which indicated marginal visual flight rules conditions. However, upon arrival in the vicinity of the airport, instrument meteorological conditions prevailed with visibility at or below the approach's visibility minimums. However, the pilot contacted the controller, obtained the weather information, and chose to continue the approach. Radar data showed that the airplane's final approach course was unstabilized. The last data point along the final approach course was about 0.5 mile southwest of the missed approach point, which was near the runway 4 approach end at an altitude of 1,100 ft. The missed approach procedure was to climb to 2,500 ft, make a climbing left turn to 4,000 feet, proceed direct to the outer marker, and hold. The lack of radar data points below 1,100 feet between the approach and departure ends of runway 4 may indicate that the airplane was below 1,100 ft over the runway area, which may indicate that the pilot attempted to visually acquire the runway environment with visibilities that did not allow for adequate visual reference to land. Likely unable to see the runway, the pilot notified air traffic control that he was executing a missed approach. The airplane impacted a wooded area about 0.39 mile north/northwest of the runway 4 departure end. The wreckage path length and slope through the trees was consistent with a shallow angle of impact at relative high speed. It is likely that the pilot continued flight below the minimum descent altitude without visually acquiring the runway and did not execute the missed approach procedures in a timely manner. Examination of the wreckage did not reveal any anomalies that would have precluded normal operation of the airplane. The filed alternate airport for the flight showed weather about the time of the accident that was above weather minimums for a precision approach that was available at the alternate airport.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Miscellaneous/other during approach (IFR missed approach)
  2. Loss of control in flight during approach (IFR missed approach) defining event
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Delayed action › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
  • factor Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below approach minima › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land
  • Flight time: 627 hours in all; 348 in this make and model; 53 in the last 90 days; 31 in the last 30 days; 494 as pilot in command
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Last inspection: annual inspection
  • Landing gear: retractable
  • Engine 1: Continental (piston); 0 hours total
  • Engine 2: Continental (piston); 0 hours total

The flight

  • Departed from: OFP Richmond VA at 3:25 pm
  • Destination: PHN Port Huron MI
  • Flight plan: IFR
  • Runway 4, 5,104 ft by 100 ft

Weather at the time

  • Light: daylight
  • Visibility: 0.2 statute miles
  • Sky: overcast at 200 ft
  • Temperature: 43°F (6°C), dew point 43°F (6°C)
  • Altimeter: 29.40 inHg
  • Observation at 10:57 pm from PHN, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.