ASN Wikibase Occurrence # 44953
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: | Monday 19 January 2004 |
| Time: | 01:06 |
| Type: |  Piper PA-28-181 |
| Owner/operator: | Pan Am International Flight Academy Inc. |
| Registration: | N298PA |
| MSN: | 2843507 |
| Year of manufacture: | 2002 |
| Total airframe hrs: | 1805 hours |
| Engine model: | Lycoming O-360-A4M |
| Fatalities: | Fatalities: 2 / Occupants: 3 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Fort Pierce, FL -
 United States of America
|
| Phase: | Approach |
| Nature: | Training |
| Departure airport: | West Palm Beach, FL (PBI) |
| Fort Pierce, FL (FPR) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The airplane was on a night instrument training flight in actual instrument meteorological conditions, with a flight instructor, a private pilot-rated student, and a private pilot-rated passenger on board. The flight was cleared for an instrument landing system (ILS) approach to runway 09. As part of the clearance, the controller assigned the flight an altitude of 1,800 feet to be maintained until established on the approach. The pilot read back the altitude incorrectly as 1,200 feet, and the controller did not correct the error. Radar service was terminated, and the pilot was cleared to change frequencies. The pilot told the controller that he planned to make a full stop landing. There were no further transmissions from the airplane. According to the passenger, the flight instructor had taken control of the airplane "due to the fact that the visibility was so poor." The passenger stated that "there was no visibility." The last thing the passenger recalled prior to impact was that "the VSI [vertical speed indicator] was dropping more than 500 ft per min." Radar data showed the airplane tracking the ILS course. The data showed the airplane crossing the outer marker at a mode C altitude of about 1,300 feet (corresponding to an altitude of 1,200 feet when corrected for local altimeter setting). This was below the 1,800 foot glideslope intercept altitude at the outer marker shown on the approach plate. The airplane remained at 1,300 feet for the next 49 seconds and then began to descend. The last radar return was recorded 1 minute 27 seconds later and showed the airplane at a mode C altitude of 400 feet (300 feet when corrected for local altimeter setting), approximately 1/4 mile west of the accident site. The accident occurred approximately 1/2 nautical mile west of the threshold of runway 09. The airplane was approximately 300 feet left of the extended runway centerline when it initially struck trees and then power lines about 50 feet above the ground (agl). The decision height for the approach was 223 feet msl, or 200 feet agl. Reported weather conditions at the airport near the time of the accident were overcast ceiling at 100 feet, surface visibility 5 statute miles in mist, and surface wind from the west at 7 knots. The ILS approach was flight checked by the FAA two days after the accident, and the localizer, glide slope, distance measuring equipment, locator outer marker, and middle marker all inspected satisfactory. No evidence of any pre-impact mechanical discrepancies were found with the airframe, engine, avionics or instruments that would have prevented successful completion of the approach.
Probable Cause: The flight instructor's failure to comply with the instrument approach procedure in that he descended prematurely below decision height resulting in an in-flight collision with trees, power lines and the ground. Contributing factors were the dark night light condition and the low ceiling.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20040129X00123&key=1
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 28-Oct-2008 00:45 | ASN archive | Added |
| 21-Dec-2016 19:24 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 07-Dec-2017 17:36 | ASN Update Bot | Updated [Operator, Departure 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