# Incident 19991121041709I: Amrgen AA5A, Fullerton, CA, November 21, 1999

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 21, 1999, 14:09 local time
- Place: Fullerton, CA
- Airport: Fullerton Municipal
- Damage: Minor damage
- Phase of flight: Go Round (Aborted VFR)
- Operating rules: General operating rules (Part 91)
- Location: 33.8720° N, 117.9798° W: Placed by OpenAirDocs at FULLERTON MUNI (FUL), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.8720&lon=-117.9798&mi=10
- Aircraft: N26165, registered now (https://openairdocs.org/aircraft/N26165) (OpenAirDocs)
- Registry model: Grumman American Avn. AA-5A (registry code 3960106, https://openairdocs.org/model/grumman-american-avn-aa-5a) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: AMRGEN AA5A
- Pilot flight hours: 240 total, 9 in this make and model
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19991121041709I

## Narrative

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

(-5) DURING LANDING ATTEMPT IN GUSTY WIND CONDITIONS, THE AIRCRAFT WAS REPORTED TO HAVE PORPOISED ABOUT THREE TIMES, THE PILOT INITIATED GO-AROUND PROCEDURES AND THE AIRCRAFT STRUCK THE TAXIWAY MARKER SIGN. DURING SECOND LANDING ATTEMPT, THE AIRCRAFT PORPOISED AGAIN AND THE PILOT MADE ANOTHER GO-AROUND. THE THIRD LANDING ATTEMPT WAS SUCCESSFUL.

## Other reports on N26165 (1)

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

- [Incident 20040419005569I](https://openairdocs.org/incident/20040419005569I), Apr 19, 2004: Amrgen AA5A (N26165), Fullerton, CA, Minor damage. (-23) On 4-19-04, pilot was on a straight in approach to runway 24 at Fullerton muni airport when he contacted an obstruction light with the left wing of the…

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.