# Incident 20030714014539I: Amrgen AA5B, Wagoner, OK, July 14, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 14, 2003, 10:30 local time
- Place: Wagoner, OK
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 35.9657° N, 95.3777° W: Placed by OpenAirDocs: center of Wagoner, OK, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.9657&lon=-95.3777&mi=10
- Aircraft: N4553L, registered now (https://openairdocs.org/aircraft/N4553L) (OpenAirDocs)
- Registry model: Gulfstream American AA-5B (registry code 3970106, https://openairdocs.org/model/gulfstream-american-aa-5b) (OpenAirDocs)
- Reported make and model: AMRGEN AA5B
- Reported engine: LYC O360*
- Pilot flight hours: 906 total, 6 in this make and model, 35 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030714014539I

## Narrative

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

(-23) PILOT STATED HE DEPARTED RIVERSIDE (RVS) AT 0930 ON 07/14/2003. ONE HOUR INTO THE LOCAL FLIGHT PILOT CONTACTED TULSA TOWER AND WAS GIVEN CLEARANCE THROUGH THEIR AIRSPACE BACK TO RVS. AT THAT POINT AIRCRAFT STARTED RUNNING ROUGH AND PILOT STARTED EMERGENCY PROCEDURES. THE LOSS OF POWER CAUSED THE AIRCRAFT TO NOT BE ABLE TO MAINTAIN ITS ALTITUDE, THEREFORE, THE PILOT DURING THE EMERGENCY DESCENDED BELOW RADIO COMMUNICATION LEVELS. AT THIS POINT THE PILOT CHOSE TO LAND THE AIRCRAFT IN AN OPEN AREA OF A SOD FARM BETWEEN BIXBY AND HASKELL, OKLAHOMA, LOCATED IN WAGONER COUNTY. THE PILOT THEN CALLED RIVERSIDE TOWER TO REPORT THE INCIDENT. ON 07/15/2003 THE PILOT, WHO IS ALSO AN A&P MECHANIC, TRAVELED BACK TO THE AIRCRAFT AND GROUND RAN IT, AND DETERMINED THE AIRCRAFT SAFE TO FLY FROM THE FIELD TO RVS. TROUBLE SHOOTING THE ENGINE SHOWED A BAD MAG CONDITION, AND BOTH MAGS WERE REPLACED. AIRCRAFT IS TO BE TEST FLOWN IN THE TRAFFIC PATTERN TO DETERMINE PROPER ENGINE OPERATION.

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.