# Incident 20121228028479I: Cessna 172R, Mesa, AZ, December 28, 2012

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 28, 2012, 23:37 local time
- Place: Mesa, AZ
- Airport: 85215
- Damage: No damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 33.4223° N, 111.8226° W: Placed by OpenAirDocs: center of Mesa, AZ, within about 7 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.4223&lon=-111.8226&mi=10
- Aircraft: N2098A, registered now (https://openairdocs.org/aircraft/N2098A) (OpenAirDocs)
- Registry model: Cessna 172R (registry code 2072401, https://openairdocs.org/model/cessna-172r) (OpenAirDocs)
- Registry engine: Lycoming I0360 SER A&C (registry code 41511, https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (OpenAirDocs)
- Reported make and model: CESSNA 172R
- Reported engine: LYCOMING I0360 SER A&C
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor, private pilot
- Pilot flight hours: 390 total, 170 in this make and model, 150 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20121228028479I

## Narrative

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

PILOT WAS PROVIDING INSTRUCTION IN PRACTICE AREA AND WAS RETURNING TO PHOENIX-MESA GATEWAY (IWA). HE NOTICED THAT THE DISPLAY ON THE GARMIN 430 (NAV/COM 1) WAS FLICKERING. THE GARMIN 430 THEN SHUT DOWN AND RESTARTED. SHORTLY AFTER THE UNIT RESTARTED IT SHUT DOWN COMPLETELY. THE PILOT ATTEMPTED TO USE NAV/COM 2. NAV COM 2 WAS ALSO NOT FUNCTIONING. THE PILOT THEN USED HIS CELLULAR PHONE TO CONTACT IWA TOWER. IWA TOWER, INSTRUCTED THE AIRCRAFT TO MAKE A STRAIGHT IN APPROACH TO 30 L AND EXPECT LIGHT GUN SIGNALS. THE PILOT APPROACHED THE EDGE OF THE IWA CLASS D AIRSPACE. CONCERNED THAT HE HAD NOT RECEIVED A LIGHT GUN SIGNAL, THE PILOT UTILIZED HIS MOBILE PHONE TO CONTACT TOWER. TOWER INSTRUCTED THE PILOT TO CONTINUE ON A STRAIGHT IN APPROACH TO 30L AND TO EXPECT A LIGHT GUN SIGNAL ON SHORT FINAL. THE PILOT CONTINUED AS INSTRUCTED, RECEIVED A CLEARANCE TO LAND, VIA LIGHT GUN, AND TAXIED TO PARKING USING THE LIGHT GUN SIGNALS.

THE PILOT CONCLUDED THAT HE HAD EXPERIENCED AN ALTERNATOR FAILURE AND SUBSEQUENT DRAIN OF POWER FROM THE BATTERY.

THE PILOT STATED, IN A PHONE INTERVIEW THAT PRIOR TO THE FLIGHT HE HAD TESTED THE ANNUCIATOR LIGHTS AND THAT THEY WERE FUNCTIONING, BUT HE DID NOT SEE AN ANNUCIATOR ILLUMINATED AFTER THE ALTERNATOR PRESUMABLY FAILED.

THE AIRCRAFT IS OWNED AND OPERATED BY ATP FLIGHT SCHOOLS. THE DIRECTOR OF MAINTENANCE FOR ATP FLIGHT SCHOOLS STATED THAT THE ALTERNATOR HAD FAILED AND WAS REPLACED.

NO ACTION IS BEING TAKEN AGAINST THE PILOT OR OWNER/OPERATOR

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.