# Incident 20040715012809I: Cessna 172A, Salt Lake City, UT, July 15, 2004

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 15, 2004, 23:20 local time
- Place: Salt Lake City, UT
- Airport: Salt Lake City International
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 40.7884° N, 111.9778° W: Placed by OpenAirDocs at SALT LAKE CITY INTL (SLC), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.7884&lon=-111.9778&mi=10
- Aircraft: N7440T, registered now (https://openairdocs.org/aircraft/N7440T) (OpenAirDocs)
- Registry model: Cessna 172A (registry code 2072404, https://openairdocs.org/model/cessna-172a) (OpenAirDocs)
- Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs)
- Reported make and model: CESSNA 172A
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 60 total, 10 in this make and model, 10 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040715012809I

## Narrative

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

(-23) PILOT WAS ON FLIGHT TO SALT LAKE CITY AT NIGHT. PILOT WAS INSTRUCTED TO SWITCH TO TOWER FREQUENCY, PILOT COMPLIED AND WAS NOT ABLE TO MAKE CONTACT WITH TOWER. AT THAT TIME PILOT NOTED A DISCHARGE INDICATION ON THE AMMETER, PILOT TURNED OFF ALL UNNECESSARY ELECTRONICS, ATTEMPTED TO SWITCH TO EMERGENCY CODE ON TRANSPONDER BUT INADVERTENTLY SELECTED 7500. PILOT ONLY HAD SMALL KEY CHAIN FLASH LIGHT IN COCKPIT. COCKPIT LIGHTS BEGAN TO DIM AND WENT OUT. PILOT WAS LOOKING FOR BOUNTIFUL SKYPARK AIRPORT AND REALIZED HE WOULDN'T BE ABLE TO TURN ON RUNWAY LIGHTS BECAUSE OF ELECTRICAL FAILURE SO HE HEADED FOR RUNWAY 17 AT SALT LAKE INTERNATIONAL AND LANDED WITHOUT CLEARANCE. PILOT DID NOT SEE ANY LIGHT GUN SIGNALS FROM TOWER. AIRCRAFT LANDED WITHOUT FURTHER INCIDENT.

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.