# Incident 20060318009269I: Amrgen AA5, Columbus, IN, March 18, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 18, 2006, 10:30 local time
- Place: Columbus, IN
- Airport: Columbus Municipal
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 39.2619° N, 85.8963° W: Placed by OpenAirDocs at COLUMBUS MUNI (BAK), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.2619&lon=-85.8963&mi=10
- Aircraft: N5843L, registered now (https://openairdocs.org/aircraft/N5843L) (OpenAirDocs)
- Registry model: American AA-5 (registry code 0631410, https://openairdocs.org/model/american-aa-5) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: AMRGEN AA5
- People aboard: 1
- Fatal injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 44 total, 44 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/20060318009269I

## Narrative

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

(-23) ON MARCH 18, 2006, A 1972 AMERICAN GRUMAN AA5, WAS BEING OPERATED BY A STUDENT PILOT AT THE COLUMBUS INDIANA MUNICIPAL AIRPORT (KBAK). PURPOSE OF THE FLIGHT WAS TO CONDUCT TAKE-OFF AND LANDINGS, AT A CONTROL TOWERED AIRPORT, IN PREPARATION FOR HIS PRIVATE PILOT PRACTICAL TEST. ON HIS FIRST LANDING, THE NOSE GEAR STRUCK HARD BOUCING THE AIRCRAFT BACK INTO THE AIR. THE PILOT "WENT AROUND" FLYING A NORMAL PATTERN FOR A FULL STOP LANDING. THIS WAS FOLLOWED BY A THIRD LANDING AND THEN A RETURN TO HIS BASE AIRPORT IN SHELBYVILLE IN. IT WAS THERE THAT HE FOUND HE HAD DAMAGED BOTH BLADES OF HIS PROPELLER DURING HIS FIRST LANDING ATTEMPT. THERE IS NO OTHER DAMAGE TO THE AIRCRAFT. ^PRIVACY DATA OMITTED^

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.