# Accident 20200713008492A: Cessna 172S, Fort Lauderdale, FL, July 13, 2020 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: July 13, 2020, 11:46 local time - Place: Fort Lauderdale, FL - Damage: Substantial damage - Collision: Collision on the ground - Phase of flight: Taxi - Operating rules: General operating rules (Part 91) - Location: 26.1983° N, 80.1631° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=26.1983&lon=-80.1631&mi=10 - Aircraft: N5280D, registered now (https://openairdocs.org/aircraft/N5280D) (OpenAirDocs) - Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs) - Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs) - Reported make and model: CESSNA 172S - Reported engine: LYCOMING IO-360-L2A - People aboard: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - Pilot flight hours: 900 total - NTSB investigation: [NTSB ERA20LA247](https://openairdocs.org/ntsb/ERA20LA247) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20200713008492A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. WHEN: JULY 13, 2020 1546 ZULU WHERE: CESSNA 172S, REGISTRATION N5280D WITH ONE PERSON ON BOARD TAXIING FROM THE CUSTOMS FACILITY TO TAXIWAY C AT FORT LAUDERDALE EXECUTIVE AIRPORT. N5280D CONTACTED A BRITTEN-NORMAN BN-2A-27, REGISTRATION N200MU, WITH ONE PERSON ON BOARD, TAXIING TO RUNWAY 27 VIA TAXIWAY E ? C ? RUNWAY 27. N5280D CAME TO REST AT THE INTERSECTION OF TAXIWAY E AND C FACING NORTHEAST AFTER CONTACT WAS MADE. N200MU CAME TO REST AT THE INTERSECTION OF TAXIWAY E AND C FACING ROUGHLY EAST. WHAT: PART 91 OPERATION, PILOT?S NAME ^PRIVACY DATA OMITTED^, OPERATED A CESSNA 172S, REGISTRATION N5280D. AIRPLANE WAS OPERATING VFR BY ^PRIVACY DATA OMITTED^ CONDUCTING PERSONAL FLIGHT OPERATIONS. PART 135 OPERATION, PILOTS NAME ^PRIVACY DATA OMITTED^, OPERATED A BRITTEN-NORMAN BN-2A-27, REGISTRATION N200MU. AIRPLANE WAS OPERATING VFR BY ^PRIVACY DATA OMITTED^ CONDUCTED PART 135 COMPANY FLIGHT OPERATIONS, WHO: PILOT IN COMMAND (PIC): ^PRIVACY DATA OMITTED^ ( #^PRIVACY DATA OMITTED^ ) ^PRIVACY DATA OMITTED^ MEDICAL CERTIFICATE SECOND CLASS: DATE OF EXAMINATION 10/24/2019 EXAMINATION OF THE AIRCRAFT AND CRASH SITE: AIRPLANE N5280D CAME TO REST AT THE INTERSECTION OF TAXIWAY E AND C FACING NORTHEAST AFTER CONTACT WAS MADE. AIRPLANE N200MU CAME TO REST AT THE INTERSECTION OF TAXIWAY E AND C FACING ROUGHLY EAST. VISUAL OBSERVATION SHOWED THAT N5280D LEFT WING DAMAGED WHILE STILL IN CONTACT WITH N200MU RIGHT PROP., HOUSING, AND WING. DEBRIS FROM BOTH AIRCRAFT LITTERED THE GROUND ON THE TAXIWAY INTERSECTION WHERE CONTACT WAS MADE. MISCELLANEOUS: ON MONDAY JULY 13, 2020, I RECEIVED A CALL FROM THE REGIONAL OPERATIONS CENTER (ROC) OF A TAXIWAY INCIDENT AT FORT LAUDERDALE EXECUTIVE AIRPORT. AN AIRPLANE WAS OPERATING PART 91 THAT CAME IN TO CONTACT WITH A PART 135 AIRPLANE ON THE TAXIWAY. THE PILOT OF THE C172 (^PRIVACY DATA OMITTED^) DID NOT SUSTAIN ANY INJURIES AND NEITHER DID THE PILOT OF THE BN-2A-27 (^PRIVACY DATA OMITTED^). BOTH PILOTS WERE ON SCENE TO GIVE STATEMENT AFTER THE CRASH. THE PILOT OF THE 172 STATES THAT HE WAS CLEARED TO TAXI CUSTOMS, TO G, C TO RUNWAY 27. THE PILOT OF THE BN-2A-27 STATES THAT HE WAS CLEARED TO TAXI FROM THE KILO RAMP TO RUNWAY 27 VIA B, E, C (CROSSING RUNWAY 31). BOTH AIRCRAFT CAME IN TO CONTACT WITH EACH OTHER AT THE INTERSECTION OF C AND E. ## Other aircraft in the event - N200MU, Britten-Norman BN-2A-27: [Accident 20200713008502A](https://openairdocs.org/incident/20200713008502A) ## 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 ERA20LA247](https://openairdocs.org/ntsb/ERA20LA247), Jul 13, 2020: Cessna 172 (N5280D), Fort Lauderdale, FL, substantial damage. Probable cause: The failure of both pilots to see and avoid each other while taxiing, which resulted in a ground collision. Contributing to the accident was the tower controller’s failure to provide information to… ## Other reports on N5280D (2) Matched to the same aircraft by N-number and date. - [Incident 20110917020809I](https://openairdocs.org/incident/20110917020809I), Sep 17, 2011: Cessna 172S (N5280D), Hollywood, FL, Minor damage. Pilot was demonstrating a forward slip to a landing. When he landed long, he decided he did not have sufficient runway remaining for a take off. Pilot elected… - [Accident 20040417005419A](https://openairdocs.org/incident/20040417005419A), Apr 17, 2004: Cessna 172S (N5280D), Key West, FL, Substantial damage. (-23) N5280D was cleared to land rwy 9. The aircraft touched down in the first 1200FT of the runway, bounced and collapsed the right main landing gear it… 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.