# Incident 20180707024629I: Cessna 172R, Fort Worth, TX, July 7, 2018

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 7, 2018, 20:15 local time
- Place: Fort Worth, TX
- Airport: Meacham
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 32.7254° N, 97.3208° W: Placed by OpenAirDocs: center of Fort Worth, TX, within about 11 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.7254&lon=-97.3208&mi=10
- Aircraft: N81AF, a cancelled registration (https://openairdocs.org/deregistered/N81AF-2019-07-10) (OpenAirDocs)
- Registry model: Cessna 172R (registry code 2072401, https://openairdocs.org/model/cessna-172r) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: CESSNA 172R
- Reported engine: LYCOMING I0360 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 80 total, 67 in this make and model, 12 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20180707024629I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON 07/07/2018 AT APPROXIMATELY 1900 CENTRAL STANDARD TIME (CST), AIRMAN ^PRIVACY DATA OMITTED^ ^PRIVACY DATA OMITTED^ WAS PILOT-IN-COMMAND OF AIRCRAFT N81AF. THE FIGHT WAS OPERATING UNDER 14 CODE OF FEDERAL REGULATIONS (CFR) PART 91, RULES GOVERNING OPERATIONS IN VISUAL METEOROLOGICAL CONDITIONS (VMC).  AIRMAN ^PRIVACY DATA OMITTED^ STATED HE ALONG WITH A PASSENGER WERE CONDUCTING A PLEASURE FLIGHT, DEPARTING AND RETURNING TO THE FORT WORTH MEACHAM INTERNATIONAL AIRPORT, AIRPORT IDENTIFIER FTW. IN ADDITION, THAT HE HAD RECEIVED THE CURRENT WIND/FORECASTED WEATHER CONDITION(S) BEFORE THE FLIGHT.

AIRMAN ^PRIVACY DATA OMITTED^ STATED THAT FTW OPERATIONAL CONTROL TOWER WAS DIRECTING HIM/AIRCRAFT N81AF AND ANOTHER AIRCRAFT IN THE TRAFFIC PATTERN FOR APPROACH, HE/AIRCRAFT N81AF WAS POSITIONED SECOND TO APPROACH/LAND. HOWEVER, FTW OPERATIONAL CONTROL TOWER RE-SEQUENCED HIM/AIRCRAFT N81AF TO LAND FIRST, DURING THE APPROACH PHASE.  AIRMAN ^PRIVACY DATA OMITTED^ STATED, THIS CAUSED A STATE OF URGENCY, ALONG WITH HAVING DIFFICULTY HEARING RADIO TRANSMISSION AND ATC DIRECTIONS. THE ?GO FIRST TO LAND? PROCESS COMPLICATED THE APPROACH, WITH SO MANY DISTRACTIONS; THE AIRCRAFTS CONTROL AND LOSS OF SITUATION AWARENESS CAUSE A HARD LANDING.

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.