# Accident 19900310003779A: Cessna 172N, Arlington, TX, March 10, 1990

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 10, 1990, 17:15 local time
- Place: Arlington, TX
- Airport: Arlington Municipal Airport
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 32.6699° N, 97.0991° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=32.6699&lon=-97.0991&mi=10
- Aircraft: N5193F, a cancelled registration (https://openairdocs.org/deregistered/N5193F-2013-08-15) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYC O320H2AD
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 938 total, 200 in this make and model, 218 in the last 90 days
- NTSB investigation: [NTSB FTW90LA080](https://openairdocs.org/ntsb/FTW90LA080) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19900310003779A

## Narrative

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

RAN OUT OF FUEL ON A FLIGHT TO CHECK OUT A PROSPECTIVE RENTER. FUEL GAUGE WAS OFF AND NO VISUAL FUEL CHECK.

## 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 FTW90LA080](https://openairdocs.org/ntsb/FTW90LA080), Mar 10, 1990: Cessna 172N (N5193F), Arlington, TX, substantial damage. Probable cause: INSTRUCTOR PILOT'S INADEQUATE PREFLIGHT PROCEDURES AND FAILURE TO ASSURE AN ADEQUATE FUEL SUPPLY FOR THE PROPOSED FLIGHT WHICH LED TO THE ENSUING ENGINE FAILURE DUE TO FUEL EXHAUSTION. FACTORS IN THE…

## Other reports on N5193F (3)

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

- [Incident 19891005054259I](https://openairdocs.org/incident/19891005054259I), Oct 5, 1989: Cessna 172N (N5193F), Dallas, TX. Low oil pressure. Precautionary landing. Left tire blew on rollout. Exited runway onto grass to clear runway.
- [Incident 19870627076449I](https://openairdocs.org/incident/19870627076449I), Jun 27, 1987: Cessna 172N (N5193F), Bridgeport, TX, Minor damage. Power loss. Forced downwind landing on airport. Overran runway hitting ditch. Engine problem not identified.
- [Incident 19850902049619I](https://openairdocs.org/incident/19850902049619I), Sep 2, 1985: Cessna 172N (N5193F), Dallas, TX, Minor damage. During night taxi in unfamiliar area pilot mistook road for taxiway. Wing struck fence post with minor damage.

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.