# Accident 20250709016639A: Piper PA-34-200, Fort Lauderdale, FL, July 9, 2025 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: July 9, 2025, 23:00 local time - Place: Fort Lauderdale, FL - Airport: Fort Lauderdale Executive - Damage: Substantial damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 26.1982° N, 80.1745° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=26.1982&lon=-80.1745&mi=10 - Aircraft: N1293T, registered now (https://openairdocs.org/aircraft/N1293T) (OpenAirDocs) - Registry model: Piper PA-34-200 (registry code 7103405, https://openairdocs.org/model/piper-pa-34-200) (OpenAirDocs) - Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs) - Reported make and model: PIPER PA-34-200 - Reported engine: LYCOMING I0360 SER - People aboard: 2 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Commercial pilot, flight instructor, private pilot, student - Pilot flight hours: 372 total, 9 in this make and model, 52 in the last 90 days - NTSB investigation: [NTSB ERA25LA263](https://openairdocs.org/ntsb/ERA25LA263) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20250709016639A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. NTSB ACCIDENT NO.: ^PRIVACY DATA OMITTED^ ATQA: A-SO-19-25-052 SAS PTRS NO.: SO19202600761 TASK ID: T-SO19-FY25-0927 REGISTRATION: ^PRIVACY DATA OMITTED^ MAKE: PIPER MODEL: PA-34-200 SERIAL NUMBER: 34-7250283 WHEN: JULY 9, 2025 WHERE: FORT LAUDERDALE EXECUTIVE (FXE) : ON JULY 9, 2025, AT APPROXIMATELY 2300 LOCAL TIME, ^PRIVACY DATA OMITTED^ WAS LANDED GEAR UP ON RUNWAY 9. THE AIRCRAFT MADE FIRST RUNWAY CONTACT APPROXIMATELY 300FT WEST OF TWY A4. THERE DID NOT APPEAR TO BE ANY TIRE MARKS PRIOR TO THE START OF ASPHALT SCORING FROM THE PROPELLORS. THE AIRCRAFT SLID TO A STOP, WITHOUT LEAVING THE RUNWAY SURFACE, IN THE INTERSECTION OF RWY 9/27 AND RWY 13/31, CAUSING BOTH RUNWAYS TO BE CLOSED. NO AIRPORT ELECTRICAL INFRASTRUCTURE WAS DAMAGED BUT THERE WAS LIGHT ASPHALT SCORING AND SCRAPES ON THE SURFACE OF RWY 9/27. WESTWAY TOWING WAS DISPATCHED AND ARRIVED AT 0155L. WESTWAY USED A ROTATOR CRANE TRUCK TO LIFT THE AIRCRAFT, AND THE PILOT DEPLOYED ALL OF ALL OF THE LANDING GEARS. THE AIRCRAFT WAS TOWED AS NORMAL TO ATLANTIC EAST ON THE S-RAMP. BOTH RUNWAYS WERE INSPECTED AND RETURNED TO ATC AT 0254L. THE AIRCRAFT WAS OPERATED BY A STUDENT ^PRIVACY DATA OMITTED^ (CERT#: ^PRIVACY DATA OMITTED^) AND INSTRUCTOR ^PRIVACY DATA OMITTED^ (CERT#: ^PRIVACY DATA OMITTED^). THERE WERE 2 SOULS AND APPROXIMATELY 20 GALLONS OF FUEL ON BOARD. THERE WAS NO HAZMAT AND NO INJURIES. ON 11JULY2025 AN INSPECTOR FROM SO19 INSPECTED AIRCRAFT POST ACCIDENT AND FOUND SUBSTANTIAL DAMAGE TO UNDERCARRIAGE OF AIRCRAFT. IN ADDITION TO THE SUBSTANTIAL DAMAGE, THE FOLLOWING ITEMS WERE OBSERVED DURING INSPECTION OF AIRCRAFT. 1) LEFT ENGINE PROPELLER WAS FEATHERED, 2) AN LED LIGHT STRIP WAS OBSERVED INSTALLED UNDERNEATH THE GLARE SHIELD OF THE AIRCRAFT. THE AIRCRAFT RECORDS WERE REVIEWED ON THE FAA DATABASE WHICH REVEALED NO RECORD OF MAJOR ALTERATION FAA FORM 337 FOR INSTALLATION OF THE LED LIGHT STRIP UNDERNEATH THE GLARESHIELD. THE LED LIGHT STRIP WAS NOT DIMMABLE. THE LED LIGHT STRIP WAS SUBSEQUENTLY REMOVED FROM THE AIRCRAFT BY THE ^PRIVACY DATA OMITTED^/OPERATOR. PILOT STATEMENTS FROM STUDENT INDICATE STEEP TURN TO FINAL TO RUNWAY 9, ADS-B DATA CORROBORATE A 1 MILE BASE TO FINAL ON RUNWAY 9. PILOT STATEMENT ALSO INDICATED A HORN WAS ACTIVATE DURING THIS FINAL APPROACH. PILOT STATEMENT FROM CFI INDICATES A SHORT FINAL TO RUNWAY 9. THE STUDENT WAS NOT MULTI ENGINE RATE THEREFORE THE CFI WAS THE PILOT IN COMMAND OF THE AIRCRAFT. BASED ON WITNESS STATEMENTS, POST CRASH EXAMINATION OF AIRCRAFT, ADS-B DATA, STATEMENTS FROM AIRPORT AUTHORITY, THE MOST LIKELY PROBABLE CAUSE OF THIS ACCIDENT IS PILOT ERROR, WHEN THE PIC FAILED TO LOWER THE LANDING GEAR DURING SHORT BASE TO FINAL APPROACH TO RUNWAY 9 @ FXE. THIS RESULTED CONTRIBUTING FACTORS OF MISMANAGED GEAR AND LOSS OF CONTROL. THE LED LIGHT WAS ALSO IMPROPER MAINTENANCE CONTRIBUTING FACTOR TO THE ACCIDENT WHICH PREVENTED VISUAL CONFIRMATION OF GEAR DOWN FROM THE MIRRORS ON THE ENGINE COWLINGS AND PREVENTED THE PIC FROM SEEING OUTSIDE THE AIRCRAFT AND WAS DISTRACTION DURING THE LANDING PHASE. I AM RECOMMENDING A 44709 REEXAMINATION OF THE CFI. ## 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 ERA25LA263](https://openairdocs.org/ntsb/ERA25LA263), Jul 10, 2025: Piper PA34 (N1293T), Fort Lauderdale, FL, substantial damage. Probable cause: The flight instructor’s inadequate supervision and delayed remedial actions during the landing approach, which resulted in the airplane contacting the runway with the landing gear retracted. ## Other reports on N1293T (3) Matched to the same aircraft by N-number and date. - [Incident 20250306001659I](https://openairdocs.org/incident/20250306001659I), Mar 6, 2025: Piper PA-34-200 (N1293T), Fort Lauderdale, FL, Minor damage. Aircraft operated under part 61 for multi-engine training/instruction. RH main landing gear collapsed after normal landing during rollout due to RH main gear… - [Incident 20240928015349I](https://openairdocs.org/incident/20240928015349I), Sep 28, 2024: Piper PA-34-200 (N1293T), St Augustine, FL, Minor damage. On 09/28/2024 the pilot under the supervision of his instructor was on approach to ksgj. After touchdown he was instructed to retract the flaps and apply… - [Incident 20230123000309I](https://openairdocs.org/incident/20230123000309I), Jan 23, 2023: Piper PA-34-200 (N1293T), Opa Locka, FL, No damage. Part 91 operation Piper PA-34-200, [privacy data omitted], practicing engine shutdown and restart in flight, pilot unable to restart left engine after four… 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.