# Incident 20011021033309I: Cessna 140, October 21, 2001

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 21, 2001, 20:45 local time
- Damage: No damage
- Operating rules: Air carrier (Part 121)
- Operator: UALA
- Aircraft: N72794, a cancelled registration (https://openairdocs.org/deregistered/N72794-2024-10-05) (OpenAirDocs)
- Registry model: Cessna 140 (registry code 2071602, https://openairdocs.org/model/cessna-140) (OpenAirDocs)
- Registry engine: Continental C85 series (registry code 17008, https://openairdocs.org/engine/continental-c85-series) (OpenAirDocs)
- Reported make and model: CESSNA 140
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20011021033309I

## Narrative

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

(-23) UAL FLIGHT 725 REPORTED ON ZKC R32 FREQUENCY AT FL280 AND STATED THAT THEY WERE DEVIATING FOR WEATHER. ATC CLEARED FLT 725 TO DESCEND TO FL240. FLT 725 EXPRESSED CONCERN ABOUT HAVING ENOUGH FUEL TO REACH MCI IF HE DESCENDED. FLT 725 WAS THE CLEARED TO FL 260. R32 ASKED FLT 725 TO REPORT WHEN ABLE TO MAKE A TURN TOWARD MCI. FLT 725 ADVISED A NEED TO TURN DIRECT TO MCI OR THEY WOULD HAVE TO DECLARE MINIMUM FUEL. R32 REPLIED HE WOULD GIVE A DIRECT ROUTING IF MINIMUM FUEL WAS DECLARED WHICH IT WAS. R32 ISSUED DESCENT TO FL240 AND FLT 725 ASKED TO STAY AT FL260 AS LONG AS POSSIBLE. R32 DECLARED AN EMERGENCY FOR FLT 725 AND ISSUED PILOT'S DISCRETION DESCENT. DUE TO ATC'S PERCEPTION OF THE FLT'S RELUCTANCE TO COMPLY W/ATC INSTRUCTIONS, THE CONTROLLER CONSIDERED THE POSSIBILITY OF A SECURITY SITUATION. INCIDENT NUMBER CE2002IAC0017 IS CONSIDERED CLOSED WITH THE FILING OF THIS REPORT - REF. PTRS #2002BO198

## Other reports on N72794 (1)

Matched to the same aircraft by N-number and date.

- [Accident 20221002016339A](https://openairdocs.org/incident/20221002016339A), Oct 2, 2022: Cessna 140 (N72794), Burnet, TX, Substantial damage. While conducting the landing a crosswind developed and caught the pilot off guard. He did not react in time to properly manage the controls leading to a ground…

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.