# Incident 20180621015609I: Mooney M20E, Mesa, AZ, June 21, 2018 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: June 21, 2018, 15:35 local time - Place: Mesa, AZ - Airport: Falcon Fld - Damage: Minor damage - Phase of flight: Landing: Rollout - Operating rules: General operating rules (Part 91) - Location: 33.4608° N, 111.7283° W: Placed by OpenAirDocs at FALCON FLD (FFZ), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=33.4608&lon=-111.7283&mi=10 - Aircraft: N3213F, a cancelled registration (https://openairdocs.org/deregistered/N3213F-2021-07-31) (OpenAirDocs) - Registry model: Mooney M20E (registry code 5870212, https://openairdocs.org/model/mooney-m20e) (OpenAirDocs) - Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs) - Reported make and model: MOONEY M20E - Reported engine: LYCOMING I0360 SER - People aboard: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - Pilot flight hours: 280 total, 30 in this make and model, 6 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20180621015609I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. THE PILOT WAS ON A VFR FLIGHT FROM MARANA KAVQ TO FALCON KFFZ WITH VFR APPROACH INTO FALCON FROM THE SOUTH EAST. HE CONTACTED ATC AND RECEIVED LANDING CLEARANCE FOR 22L. ON FINAL APPROACH HE DID NOT HAVE A GREEN LIGHT INDICATING LOCKED GEAR DOWN. BECAUSE OF THIS, HE EXECUTED A GO-AROUND AND NOTIFIED ATC OF THE POSSIBLE LANDING GEAR MALFUNCTION. HE THEN REQUESTED CLEARANCE TO CIRCLE NORTH OF THE FIELD. CLEARANCE WAS GRANTED. HE PROCEEDED TO THE HOLDING PATTERN AND SLOWED THE AIRCRAFT TO 110 MPH. HE THEN TRIED TO EXTEND THE LAND GEAR 3 OR MORE TIMES WITH THE LANDING GEAR SWITCH. THIS FAILED EACH TIME AND THE SWITCH HAD NO NOTICEABLE EFFECT. HE BEGAN FOLLOWING THE PROCEDURES IN THE AIRCRAFT EMERGENCY GEAR EXTENSION CHECKLIST, AND THEN ATTEMPTED TO EXTEND THE LANDING GEAR USING THE EMERGENCY HAND CRANK . HE WAS SUCCESSFUL IN LOWERING THE WHEELS; HOWEVER HE DID NOT ACHIEVE A GREEN "LOCKED" INDICATION. HE THEN TRIED ADDITIONAL HAND CRANKING AND AFTER -115 CRANK REVOLUTIONS, THE CRANK RESISTANCE INCREASED SHARPLY AND HE DISCONTINUED THE CRANKS. THE LANDING GEAR ALIGNMENT INDICATOR IS LOCATED BEHIND A 3" WINDOW ON THE FLOOR AND VISIBLE BY LOOKING DOWN BETWEEN THE FRONT SEATS. HE OBSERVED A HORIZONTAL BLACK LINE HAD MOVED INTO VIEW IN THE CINDER OF THE WINDOW, INDICATING THAT THE GEAR HAD BEEN LOWERED. CONCURRENTLY, THE AIRCRAFT BEGAN TO LOSE AIRSPEED FROM ADDITIONAL DRAG, AS EXPECTED WITH THE GEAR DOWN. HE THEN NOTIFIED ATC THAT HE WANTED TO LAND BUT STILL DID NOT HAVE A GREEN LOCK LIGHT. HE RECEIVED CLEARANCE FOR THE OPTION ON 22L. HE EXECUTED A GO-AROUND WITH A SLOW CLIMB TO ALLOW THE CONTROL TOWER TO MAKE A VISUAL INSPECTION OF THE AIRCRAFT LANDING GEAR. THEY CONFIRMED THAT ALL THREE WHEELS WERE DOWN. DURING THE GO-AROUND HE GOT THE AUDIBLE WARNING THAT THE GEAR WAS NOT LOCKED. HE MADE A LEFT CLOSED TRAFFIC AND THEN LANDED ON 22L. HE SAID IT FELT STABLE FOR ABOUT 1 SECOND, THEN THERE WAS A SLIGHT WOBBLE IN THE RIGHT GEAR, AND THEN ALL THE GEAR COLLAPSED. THE COLLAPSE WAS NOT QUITE SIMULTANEOUS, AND IT FELT LIKE THE RIGHT GEAR PRECEDED THE REST BY A FRACTION OF A SECOND. THE AIRCRAFT CONTACTED THE RUNWAY ON ITS BELLY. THE PROP TOUCHED THE RUNWAY AND CAUSE THE ENGINE TO STOP. THE AIRCRAFT CONTINUED TO SLIDE DOWN THE CENTERLINE OF THE RUNWAY UNTIL IT CAME TO A STOP. HE EXITED THE AIRCRAFT NORMALLY. ## Other reports on N3213F (1) Matched to the same aircraft by N-number and date. - [Incident 19781102023729I](https://openairdocs.org/incident/19781102023729I), Nov 2, 1978: Mooney M20E (N3213F), Palo Alto, CA, Minor damage. Aircraft struck ditch while taxiing at night without taxi light. Battery was too weak due to generator failure. 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.