# Incident 20131024020619I: Beech F33A, Mobile, AZ, October 24, 2013 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: October 24, 2013, 07:55 local time - Place: Mobile, AZ - Airport: Mobile - Damage: Minor damage - Phase of flight: Landing: Approach - Operating rules: General operating rules (Part 91) - Aircraft: N1556A, a cancelled registration (https://openairdocs.org/deregistered/N1556A-2014-05-16) (OpenAirDocs) - Registry model: Beech F33A (registry code 1151425, https://openairdocs.org/model/beech-f33a) (OpenAirDocs) - Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs) - Reported make and model: BEECH F33A - Reported engine: CONT MOTOR IO 520 SERIES - People aboard: 2 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Commercial pilot, flight instructor - Pilot flight hours: 2,444 total, 753 in this make and model, 184 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20131024020619I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. THE INSTRUCTOR AND STUDENT PILOT FOR N1556A DEPARTED GOODYEAR AIRPORT (KGYR) FOR MOBILE AIRPORT (1AZ0) ON THE MORNING OF 10/24/13. THE PURPOSE OF THE FLIGHT WAS TO POSITION AT 1AZ0 FOR THE STUDENT'S FIRST SOLO. PRIOR TO THE SOLO, THE CREW PLANNED TO PERFORM APPROXIMATELY 3 LANDINGS AND A SIMULATED ENGINE FAILURE IN THE PATTERN AT 1AZ0. ENROUTE TO 1AZ0, THE PILOTS RECEIVED THE AWOS WEATHER FROM BUCKEYE AIRPORT (KBXK) TO DETERMINE THE POSSIBLE WINDS AT 1AZ0. THE WINDS FAVORED LANDING ON RUNWAY 27 AT 1AZ0. THE PILOTS ENTERED A PATTERN FOR RUNWAY 27, AND LANDED WITH A "NOTICEABLE TAILWIND" OF APPROXIMATELY 6 KNOTS. AFTER PERFORMING ONE MORE PATTERN ON RUNWAY 27, THE CREW PERFORMED A FULL STOP LANDING, AND ALLOWED A BACKSEAT PASSENGER TO EXIT THE AIRCRAFT. THE CREW THEN TAXIED FOR A TAKEOFF ON RUNWAY 9. THE CREW FOLLOWED ANOTHER COMPANY AIRCRAFT IN THE PATTERN. THE CREW INITIALLY FOLLOWED NORMAL COMPANY PROCEDURES IN THE PATTERN, AND SELECTED FLAPS 15 ON DOWNWIND. ABEAM THE APPROACH END OF RUNWAY 9 ON DOWNWIND, THE INSTRUCTOR ASKED THE CREW OF THE PRECEDING AIRCRAFT IF THERE WAS ROOM FOR N1556A TO CUT IN FRONT IN THE PATTERN TO PERFORM A SIMULATED ENGINE FAILURE/ SHORT APPROACH. THE CREW OF THE PRECEDING AIRCRAFT RESPONDED THAT THERE WAS NOT ENOUGH ROOM. THE CREW OF N1556A THEN CHANGED THEIR PLANS, AND CONTINUED ON DOWNWIND FOR A NORMAL LANDING. DUE TO THE CHANGE IN PLAN, THE STUDENT PILOT HAD NOT FOLLOWED SOME TYPICAL PATTERN PROCEDURES (I.E. SETTING A TIMER ABEAM THE APPROACH END, TO TIME FOR THE TURN TO BASE). THE INSTRUCTOR THEN TOLD THE STUDENT TO TURN BASE. ACCORDING TO THE STUDENT'S STATEMENT, THE NORMAL COMPANY PROCEDURES WERE DISMISSED OR FORGOTTEN FROM THIS POINT ON. THE STUDENT DID NOT EXTEND THE GEAR, DID NOT MAKE NORMAL REDUCTION IN POWER, DID NOT TRIM FOR DESCENT, DID NOT PERFORM THE "FINAL ITEMS" AND DID NOT PERFORM THE "FINAL CHECKLIST". UPON TURNING BASE, THE STUDENT AND INSTRUCTOR BOTH REALIZED THEY WERE TOO HIGH AND FAST. THE STUDENT STATED THAT HIS FOCUS "WAS COMPLETELY ON CORRECTING THE ALTITUDE AND SPEED". THE NORMAL COMPANY CALLOUTS WERE NOT PERFORMED AT THIS TIME: "GEAR CHECKED/ RUNWAY CLEAR." THE STUDENT ALSO STATED THAT THE "GEAR WARNING HORN HAD BEEN SOUNDING SINCE END OF BASE". UPON TOUCHDOWN THE CREW REALIZED THE GEAR WAS IN THE RETRACTED POSITION. THE AIRCRAFT CAME TO A STOP APPROXIMATELY HALFWAY DOWN THE RUNWAY. UPON EXAMINATION OF THE AIRCRAFT BY THE IIC, IT WAS FOUND THAT THE GEAR HANDLE WAS IN THE RETRACTED POSITION. IT WAS ALSO FOUND THAT THE "ANNUNCIATOR TEST" SWITCH WAS IN THE "DIM" POSITION. THIS WAS LIKELY DUE TO THE FACT THAT THE AIRCRAFT HAD BEEN FLOWN ON A NIGHT MISSION PREVIOUS TO THIS FLIGHT. THIS SWITCH POSITION WOULD MAKE THE GEAR POSITION LIGHTS, AND THE GEAR WARNING LIGHT MORE DIFFICULT TO SEE DURING DAYTIME CONDITIONS. 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.