# Incident 19981022040419I: Mooney M20M, Denver, CO, October 22, 1998

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 22, 1998
- Place: Denver, CO
- Airport: Centennial Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 39.5701° N, 104.8493° W: Placed by OpenAirDocs at CENTENNIAL (APA), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.5701&lon=-104.8493&mi=10
- Aircraft: N133PR, registered now (https://openairdocs.org/aircraft/N133PR) (OpenAirDocs)
- Registry model: Mooney M20M (registry code 5870222, https://openairdocs.org/model/mooney-m20m) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: MOONEY M20M
- Reported engine: LYC TIO540AF1B
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 3,600 total, 2,500 in this make and model, 80 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19981022040419I

## Narrative

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

(-5)AS PER YOUR REQUEST DURING OUR CONVERSATION ON FRIDAY THE 6TH OF NOVEMBER, THIS IS A NARRATIVE SUMMARY OF THE EVENTS REGARDING N133PR ON THE 22ND OF OCTOBER AT APA. THE PLANE N133PR IS A MOONEY (M020) M MODEL.  THE SERIAL NUMBER OF THE AIRCRAFT IS 27-0157.  I, JAMES M. ANDRIOLE, PILOTED THE PLANE.  MY PILOT CERTIFICATE NUMBER IS 198368536, PRIVATE PILOT, AIRPLANE SINGLE ENGINE LAND AND INSTRUMENT AIRPLANE RATING.  I HAVE 2500+ HOURS IN MAKE AND MODEL, AND 80HRS IN THE LAST 90 DAYS.  ON THE 22ND OF OCTOBER, I DEPARTED TULSA, OK (RVS) TO FLY TO CENTENNIAL (APA) AIRPORT ON AN IFR FLIGHT PLAN.  I MADE RADIO CONTACT WHITH CENTENNIAL TOWER AND REPORTED THE CURRENT ATIS.  MY VICINITY WAS CASSE AND WAS TOLD BY THE TOWER 1 WAS NUMBER TWO FOR THE AIRPORT, VISUAL LANDING FOR RUNWAY 35R.  TOWER TOLD ME OF A PLANE AHEAD OF ME LANDING 35R AND IDENTIFIED THAT AIRCRAFT AS A TWIN CESSNA.  I CALLED THE AIRCRAFT IN SIGHT AND WAS TOLD TO PROCEED INBOUND FOR LANDING.  I REDUCED POWER SETTINS FURTHER, PERFORMED MY LANDING CHECKLIST, AND LOWERED THE GEAR.  TOWER INFORMED ME THEY WANTED TO GET A JET OUT AHEAD OF MY ARRIVAL.  TOWER CALLED ME AND ASKED IF I WOULD ACCEPT THE LEFT RUNWAY.  I DECLINED.  I N THAT CASE TOWER REQUESTED THAT I MAKE A 180-DEGREE TURN TO THE RIGHT AND TO EXPECT RUNWAY 35R AFTER THE JET HAD DEPARTED. AT THIS POINT I WAS WITHIN A ONE MILE FINAL AND AT 400-500FT AGL.  I COMPLID WITH THE TOWER REQUEST AND RAISED THE GEAR FOR IMPROVED PERFORMANCE TO CLIMB DUE TO TERRAIN.  TOWER THEN MADE ME NUMBER TWO TO LAND ON 35R.  AT THIS POINT I WAS APPROACH TO FINAL.  ON SHORT FINAL, I BELIEVED MY GEAR WAS DOWN AND LOCKED, BUT THE GEAR WAS NOT EXTENDED AT LANDING. UPON TOUCH DOWN THERE WAS A LOUD SCRAPING NOISE, I IMMDIATELY REALIZED WHAT HAD HAPPENED AND REACHED DOWN TO TURN THE FUEL SELECTOR AND ELECTRICAL SYSTEMS OFF.  I THEN NOTIFIED THE TOWER OF MY SITUATION.  ONCE PERSONNEL ARRIVED I REPORTED NO INJURIES TO MYSELF OR MY SERVICE DOG THAT WAS ONBOARD THE AIRCRAFT.  CENTENNIAL OPERATIONS THEN CAME OUT AND WE PROCEEDED WITH THE PAPER WORK AND NOTIFYING DUFF AIRCRAFT COMPANY TO REMOVE THE AIRPLANE FORM THE RUNWAY.  ONCE AT THE FBO, I PHONED THE TOWER AND SPOKE WITH DIANE THE SUPERVISOR TO INSURE THE INCIDENT WAS REPORTED.  I HOPE THIS INFORMATION IS WHAT WAS NEEDED.  PLEASE DO NOT HESITATE TO CONTACT ME SHOULD YOU NEED ANY OTHER INFORMATION.  SINCERELY, JAMES ANDRIOLE

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.