# Incident 19981205042199I: Diamon DA20A1, Glendale, AZ, December 5, 1998

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 5, 1998, 13:31 local time
- Place: Glendale, AZ
- Airport: Glendale Municipal Airport
- Damage: Minor damage
- Phase of flight: To Init Climb(1st Pwr Reduct)
- Operating rules: General operating rules (Part 91)
- Location: 33.5269° N, 112.2951° W: Placed by OpenAirDocs at GLENDALE RGNL (GEU), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.5269&lon=-112.2951&mi=10
- Aircraft: N524SS, a cancelled registration (https://openairdocs.org/deregistered/N524SS-2002-02-20) (OpenAirDocs)
- Registry model: Diamond Aircraft Ind DA20-A1 (registry code 2990000, https://openairdocs.org/model/diamond-aircraft-ind-da20-a1) (OpenAirDocs)
- Registry engine: Bombardier ROTAX (ALL) (registry code 09050, https://openairdocs.org/engine/bombardier-rotax-all) (OpenAirDocs)
- Reported make and model: DIAMON DA20A1
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 315 total, 35 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/19981205042199I

## Narrative

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

(-5)INCIDENT OCCURRED ON DEC. 5, 1998 DURING A DUAL TRAINING FLIGHT IN A KATANA DA20 N524SS AT GLENDALE MUNICIPAL AIRPORT, RUNWAY 19. WX:  VMC, WIND CONDITION 210/12 RUNWAY CONDITION WAS NOT A FACTOR.  DURING A NORMAL APPROACH TO LAND THE STUDENT PILOT INITIATED A TRANSITION TO LAND AT APPROXIMATELY 20 FEET ABOVE THE RUNWAY AFTER CROSSING THE RUNWAY THRESHOLD.  THE STUDENT PILOT INCORRECTLY ATTEMPTED TO ALIGN THE AIRCRAFT WITH THE RUNWAY BY BANKING LEFT WHICH RESULTED IN THE AIRCRAFT DRIFTING LEFT DUE TO THE CROSSWIND CONDITIONS.  AT THIS POINT I INSTRUCTED HIM TO GO AROUND, THE LEFT WING TIP CONTACTED THE RUNWAY BECAUSE THE STUDENT PILOT FAILED TO APPLY FULL POWER.  AT THE FIRST INDICATION THAT THE STUDENT DID NOT COMPLY WITH MY INSTRUCTIONS TO GO AROUND, I TOOK CONTROL OF THE AIRCRAFT AND ROLLED THE WINGS TO A LEVEL ATTITUDE BEFORE THE AIRCRAFT TOUCHED DOWN BEYOND THE LEFT SIDE OF RUNWAY 19.  AT THIS POINT THE TOWER CONTROLLER INQUIRED ABOUT OUR CONDITION.  I INFORMED HIM THAT WE COULD TAXI AND REQUESTED PERMISSION TO PROCEED BACK ONTO THE RUNWAY AND TAXI TO PARKING.  FOLLOWING THIS EVENT I SECURED THE AIRCRAFT, IMMEDIATELY INFORMED THE CHIEF PILOT, AND CONTACTED THE CONTROL TOW ER, AS THEY REQUESTED. THIS FLIGHT WAS THE LESSON FOLLOWING THE INTRODUCTION OF CROSSWIND LANDINGS, IN ADDITION, A PREFLIGHT DISCUSSION WAS CONDUCTED COVERING CROSSWIND LANDINGS.  THE STUDENT PILOT IS SCHEDULED TO BE EVALUATED BY THE CHIEF PILOT ON DEC 8/98 AT 15:00, IN ADDITION A GROUND SESSION WILL BE USED TO DISCUSS THIS EVENT BEFORE CONTINUING HIS TRAINING.  SUBMITTED BY PILOT:  BEKIM D. FAUSETT CERTIFICATE NUMBER 100788748  CERTIFICATES:  COMMERCIAL MEL, CFII, T.T.315

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.