ASN Wikibase Occurrence # 172507
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Wednesday 24 December 2014 |
| Time: | 12:54 |
| Type: |  Piper PA-34-200T Seneca II |
| Owner/operator: | Private |
| Registration: | N38884 |
| MSN: | 34-7770352 |
| Year of manufacture: | 1977 |
| Engine model: | Continental |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | St Clair County Int'l Airport (KPHN), Port Huron, MI -
 United States of America
|
| Phase: | Approach |
| Nature: | Executive |
| Departure airport: | Richmond, VA (OFP) |
| Port Huron, MI (PHN) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Probable Cause: 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.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 25-Dec-2014 01:03 | Geno | Added |
| 29-Dec-2014 19:57 | Geno | Updated [Registration, Source, Damage, Narrative] |
| 08-Jan-2015 04:35 | Geno | Updated [Time, Nature, Source] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 30-Nov-2017 19:43 | ASN Update Bot | Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation