# Incident 20051003027069I: Piper PA28R200, Albuquerque, NM, October 3, 2005

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 3, 2005, 11:15 local time
- Place: Albuquerque, NM
- Airport: Double Eagle II Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 35.1449° N, 106.7952° W: Placed by OpenAirDocs at DOUBLE EAGLE II (AEG), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.1449&lon=-106.7952&mi=10
- Aircraft: N43496, registered now (https://openairdocs.org/aircraft/N43496) (OpenAirDocs)
- Registry model: Piper PA-28R-200 (registry code 7102811, https://openairdocs.org/model/piper-pa-28r-200) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: PIPER PA28R200
- Reported engine: LYC IO360LYC*
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 253 total, 25 in this make and model, 1 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20051003027069I

## Narrative

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

(-23) ON OCTOBER 3, 2005, AT APPROXIMATELY 11:15 MDT, A PIPER PA-28R-200 LANDED ON RUNWAY 22 WITH THE LANDING GEAR RETRACTED AT THE DOUBLE EAGLE AIRPORT, ALBUQUERQUE, NM. ACCORDING TO THE CERTIFIED FLIGHT INSTRUCTOR AND HIS PRIVATE PILOT RATED STUDENT (PILOT IN COMMAND), THEY WERE PRACTICING TAKEOFFS AND LANDINGS IN PREPARATION FOR THE STUDENTS UPCOMING FLIGHT TEST. ON THE 6TH LANDING OF THE LESSON, THE FLIGHT INSTRUCTOR STATED THAT HE NEVER RECALLED HEARING THE LANDING GEAR WARNING HORN WHEN ENGINE POWER WAS RETARDED. THE FLIGHT INSTRUCTOR STATED THAT THEY BECAME FIXATED WITH MAKING THE LANDING APPROACH AND FAILED TO CONFIRM THAT THE LANDING GEAR WAS IN THE DOWN POSITION PRIOR TO LANDING. AIRCRAFT DAMAGE WAS CONTAINED TO PROPELLER, WING FLAPS AND OF THE LOWER FUSELAGE AS A RESULT. THERE WAS NO POST INCIDENT FIRE OR INJURIES TO THE INSTRUCTOR AND STUDENT. POST INCIDENT INSPECTION OF THE AIRCRAFT REVEALED NO ABNORMALITIES ASSOCIATED WITH THE LANDING GEAR SYSTEM. FURTHERMORE, REVIEW OF AIRCRAFT MAINTENANCE RECORDS REVEALED NO ABNORMALITIES RELATED TO THE OPERATION OF THE AIRCRAFT. WEATHER CONDITIONS AT THE TIME OF THE INCIDENT WERE VFR.

## Other reports on N43496 (4)

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

- [Incident 20151016020979I](https://openairdocs.org/incident/20151016020979I), Oct 16, 2015: Piper PA-28R-200 (N43496), Pineville, LA, Minor damage. CFI gave student pilot a simulated engine failure while on cross wind. During return to field to land downwind landing gear was not extended.
- [Incident 20020128001879I](https://openairdocs.org/incident/20020128001879I), Jan 28, 2002: Piper PA28R200 (N43496), Albuquerque, NM, Minor damage. (-23) On January 28, 2002 at 0830 MST, a Piper PA28R-200, N43496 registered to aero meridian inc., obtained minor damage upon landing after the nose gear…
- [Incident 19910529022809I](https://openairdocs.org/incident/19910529022809I), May 29, 1991: Piper PA28R200 (N43496), Albuquerque, NM, Minor damage. Nose gear collapsed on landing rollout. MAS464P4-31 bolt in the link and brace assembly gear down lock had broken.
- [Accident 19801128074439A](https://openairdocs.org/incident/19801128074439A), Nov 28, 1980: Piper PA28R200 (N43496), Mountain Home, AR, Substantial damage. Ran off side of runway avoiding a deer that ran across runway in front of the landing airplane.

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.