Piper PA-28-181 N298PA
19 January 2004 · Fort Pierce, Florida, United States · Fatal
Summary
On 19 January 2004 at about 06:06 local time, a Piper PA-28-181 registered N298PA, operated by Pan Am International Flight Academy Inc., was involved in an accident near Fort Pierce, Florida, United States. 3 people were on board and 2 died, one was seriously injured. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 06:06
- Classification
- Accident
- Location
- Fort Pierce, Florida, United States
- Nearest airport
- St. Lucie County International (FPR)
- Coordinates
- 27.4858, -80.3844
- Aircraft
- Piper PA-28-181
- Registration
- N298PA
- Category
- Airplane
- Engines
- 1
- Operator
- Pan Am International Flight Academy Inc.
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Instructional
- Phase of flight
- Not recorded
- Route
- West Palm Beach → Fort Pierce
- Aircraft damage
- Destroyed
- Weather
- IMC
- Light
- Night
- NTSB number
- MIA04FA045
People
2 people died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 3 | 2 | 1 | 0 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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.
Quoted verbatim from the NTSB record.
Other Piper PA-28 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 13 May 2004 | Piper PA-28-161 | Tucson, Arizona, United States | IATA Inc. | No injuries | - |
| 18 Sep 2004 | Piper PA-28-180 | Hurdland, Missouri, United States | - | Minor injuries | - |
| 31 Jul 2004 | Piper PA-28-140 | Custer, South Dakota, United States | Flight Training Adventure Camps | No injuries | - |
| 8 Dec 2004 | Piper PA-28-161 | Kapolei, Hawaii, United States | - | No injuries | - |
| 23 Jun 2004 | Piper PA-28-181 | Fort Lauderdale, Florida, United States | - | Fatal | 2 |
| 24 Mar 2004 | Piper PA-28-180 | Norwood, Massachusetts, United States | - | No injuries | - |
All 9,402 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 2 Oct 2004 | Robinson R-22 | Pompano Beach, Florida, United States | - | Minor injuries | - |
| 12 Mar 2004 | Robinson R22 | Keystone, Florida, United States | Collective Helicopter Corp | No injuries | - |
| 13 Mar 2004 | Beechcraft BE90 | Fort Lauderdale, Florida, United States | Execstar Aviation Inc | No injuries | - |
| 1 Oct 2004 | Rotorway 162F | New Smyrna Beac, Florida, United States | - | No injuries | - |
| 6 May 2004 | Beechcraft H35 | Fort Pierce, Florida, United States | Tim Sullivan | Minor injuries | - |
| 20 Oct 2004 | Eurocopter Deutschland BO-105 CBS5 | Santa Rosa Bch, Florida, United States | - | Fatal | 3 |