# Accident 20050325006099A: Piper PA23250, West Palm Beach, FL, March 25, 2005 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: March 25, 2005, 12:30 local time - Place: West Palm Beach, FL - Airport: Palm Beach International - Damage: Substantial damage - Phase of flight: Roll-Out (Fixed Wing) - Operating rules: General operating rules (Part 91) - Location: 26.6831° N, 80.0956° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=26.6831&lon=-80.0956&mi=10 - Aircraft: N11EG, a cancelled registration (https://openairdocs.org/deregistered/N11EG-2007-05-23) (OpenAirDocs) - Registry model: Piper PA-23-250 (registry code 7102308, https://openairdocs.org/model/piper-pa-23-250) (OpenAirDocs) - Registry engine: Lycoming 0-540 series (registry code 41532, https://openairdocs.org/engine/lycoming-0-540-series) (OpenAirDocs) - Reported make and model: PIPER PA23250 - People aboard: 1 - Fatal injuries: 0 - Pilot flight hours: 1,300 total, 1,000 in this make and model, 20 in the last 90 days - NTSB investigation: [NTSB MIA05CA082](https://openairdocs.org/ntsb/MIA05CA082) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20050325006099A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) ON 03/25/2005 INSPECTOR ^PRIVACY DATA OMI^ AND I WERE DISPATCHED TO PALM BEACH INTERNATIONAL AIRPORT (PBI) AT APPROXIMATELY 12:30 LOCAL TIME TO INVESTIGATE AN ACCIDENT INVOLVING A PILOT NAMED ^PRIVACY DATA OMITT^, OPERATING A PIPER AZTEC N11EG. I SPOKE WITH THE PILOT/OWNER, ^PRIVACY DATA OM^ ON HIS CELL PHONE AND ASKED HIM TO REMAIN WITH THE AIRCRAFT AFTER HE CLEARED CUSTOMS. HIS FLIGHT ORIGINATED IN TREASURE CAY, IN THE BAHAMAS, VFR TO PALM BEACH INTERNATIONAL AIRPORT (PBI) FOR CUSTOMS AND CONTINUING TO LANTANA AIRPORT, HIS HOME BASE. THE PILOT ^PRIVACY DAT^ STATED THAT HE HAD TO GO GET HIS CAR AND GO HOME. UPON ARRIVAL AT THE SCENE, WE FOUND THE AIRCRAFT TO BE REMOVED FROM THE CRASH SITE AND LOCATED ON THE RAMP AREA. THE DAMAGE TO THE AIRPLANE APPEARED TO BE SIGNIFICANT WITH THE NOSE GEAR COLLAPSED, NOSE CONE DAMAGE INFLICTED, AND BOTH ENGINE PROP BLADES BENT. AFTER CHECKING THE AIRCRAFT DOCUMENTS AND GENERAL CONDITION OF THE AIRPLANE, WE WALKED THE TRACK FROM THE TOUCHDOWN POINT ON A CLOSED TAXIWAY, ALONG THE SKID MARKS SOME 1200' FROM THE PAVED TOUCHDOWN POINT, OFF INTO THE GRASS, ACROSS ANOTHER TAXIWAY, DOWN A SMALL DEPRESSION TO WHERE THE NOSE GEAR APPARENTLY DUG IN, WAS COLLAPSED, AND THE PROP BLADES STRUCK THE GROUND. WE ACCESSED THE AIRCRAFT, CHECKED THE APPROPRIATE DOCUMENTS, ASSESSED SWITCH AND HANDLE LOCATION, AND ALL APPEARED IN ORDER. WE ACCOMPLISHED A CURSORY INSPECTION OF THE EXTERIOR OF THE AIRCRAFT FOR AN INITIAL DAMAGE ASSESSMENT. INSPECTOR ^PRIVACY DA^ AND I THEN INTERVIEWED THE PILOT ^PRIVACY DAT^ AT HIS RESIDENCE. I LOOKED AT HIS PILOT CERTIFICATE AND MEDICAL DOCUMENTS, AND PERSONAL LOGBOOKS WHICH WERE IN ORDER. THE AIRCRAFT AND ENGINE LOG BOOKS WERE EXAMINED AND FOUND TO BE IN ORDER WITH GOOD FORMAT. I HAVE REVIEWED THE INITIAL AUDIO TAPE FROM PBI ATC, AND COMPARED THEM WITH THE PILOT'S STATEMENT. THERE ARE SOME DISCREPANCIES IN INTERPRETATION. ON THE DAY OF THE ACCIDENT, THE AIRCRAFT INITIALLY CONTACTED ATC APPROACH CONTROL 20 MILES EAST FOR LANDING AT PBI. N11EG WAS "HANDED OFF" TO THE TOWER AND, SUBSEQUENTLY, CLEARED TO LAND ON RUNWAY 9R. TOWER PERSONNEL NOTED THE AIRCRAFT TO BE LINED UP ON AN ABANDONED TAXIWAY FOR THE FIRST APPROACH AND WAS TOLD TO "GO-AROUND." N11EG REJOINED THE DOWNWIND FOR A CLOSE-IN RIGHT HAND TRAFFIC, WAS CLEARED TO LAND, AND APPEARED TO HAVE, ONCE AGAIN, LINED UP WITH THE CLOSED TAXIWAY. JUST PRIOR TO THE AIRCRAFT IMPACTING THE GROUND ON A NON-APPROVED PAVED AREA, PARALLELING RUNWAY 09R, THE WINDS WERE REPORTED TO BE FROM 170 DEGREES AT 11 KNOTS. THE PILOT REPORTED GUSTY WINDS BUT NO ARRIVING TRAFFIC BEFORE AND AFTER THE INCIDENT EXPERIENCED ANY PROBLEMS. THE PILOT LANDED APPROXIMATELY 80 YARDS TO THE RIGHT OF THE DESIGNATED RUNWAY 9R. WITH THOSE WIND CONDITIONS, THE AIRPLANE SHOULD HAVE BEEN PUSHED IN THE OPPOSITE DIRECTION. THE PILOT STATED THAT HE "USUALLY COMES IN HIGH." AND ON THE SECOND APPROACH, THE PILOT STATED THAT HE CAME IN LOWER AND SLOWER AND "SLOWED THE AIRCRAFT TO 115KTS." "THE WINDS BLEW HIM TO THE RIGHT OF THE RUNWAY" AND THE PILOT MADE THE DECISION TO "PUT IT DOWN RATHER THAN TRY TO CORRECT FOR HIS DRIFT." ^PRIVACY DATA OMITTED^ ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB MIA05CA082](https://openairdocs.org/ntsb/MIA05CA082), Mar 25, 2005: Piper PA-23-250 (N11EG), West Palm Beach, FL, substantial damage. Probable cause: The failure of the pilot to maintain proper alignment with the runway, his failure to perform a go around after recognizing the aircraft was not properly aligned for landing, and his intentionally… From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.