# Incident 20150527010969I: Beech C24R, Chino, CA, May 27, 2015 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: May 27, 2015, 14:30 local time - Place: Chino, CA - Airport: Chino Airport - Damage: Minor damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 33.9748° N, 117.6365° W: Placed by OpenAirDocs at CHINO (CNO), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=33.9748&lon=-117.6365&mi=10 - Aircraft: N6698F, registered now (https://openairdocs.org/aircraft/N6698F) (OpenAirDocs) - Registry model: Beech C24R (registry code 1151254, https://openairdocs.org/model/beech-c24r) (OpenAirDocs) - Registry engine: Lycoming I0360 SER A&C (registry code 41511, https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (OpenAirDocs) - Reported make and model: BEECH C24R - Reported engine: LYCOMING I0360 SER A&C - People aboard: 2 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Airline transport, flight instructor - Pilot flight hours: 19,000 total, 150 in this make and model, 150 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20150527010969I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. WHILE CONDUCTING A LOCAL TRAINING FLIGHT WITH A FLIGHT INSTRUCTOR AND A PRIMARY (STUDENT) PILOT ON BOARD, THE AIRCRAFT WAS LANDED WITH THE LANDING GEAR IN THE UP POSITION. THE FLIGHT ORIGINATED AT THE CORONA, CA. AIRPORT (AJO) WHERE THE INSTRUCTOR WAS HAVING THE STUDENT PERFORM SHORT FIELD TAKE-OFFS AND LANDINGS. ONCE THOSE TASKS WERE COMPLETED, THE AIRCRAFT DEPARTED TO CHINO, CA. AIRPORT (CNO) FOR ADDITIONAL TRAINING. THE NORMAL ROUTINE FROM AJO IS TO ENTER LEFT DOWNWIND FOR RUNWAYS 26L AT CNO. HOWEVER, THIS DAY, THE AIRCRAFT WAS INSTRUCTED TO ENTER LEFT BASE. WHILE ON BASE LEG, TRAFFIC WAS POINTED OUT TO THE INSTRUCTOR AND STUDENT. THE INSTRUCTOR TOLD THE STUDENT TO CONFIGURE THE AIRCRAFT FOR LANDING AND THAT HE WOULD LOOK FOR TRAFFIC. AS THE AIRCRAFT WAS TURNING TOWARD FINAL, ADDITIONAL TRAFFIC ON 26R WAS CALLED OUT BY ATC. WITH THE INSTRUCTOR ATTENTION OUTSIDE LOOKING FOR TRAFFIC, THE STUDENT WAS INSTRUCTED THE TASK OF FLYING THE AIRCRAFT AND COMPLETING THE BEFORE LANDING CHECKLIST. WITH THE OUT OF NORMAL TRAFFIC PATTERN ENTRY, THE CROWED TRAFFIC PATTERN, BUSY RADIO COMMUNICATIONS, AND THE INSTRUCTOR?S ATTENTION DIVERTED OUTSIDE THE AIRCRAFT, THE STUDENT PILOT FAILED TO DEPLOY THE LANDING GEAR AND RUN THE GUMPS CHECKLIST. THE INSTRUCTOR ALSO STATES THAT ONCE ON FINAL HE DID CHECK THE LANDING GEAR LIGHTS, BUT GLARE FROM SUN MUST HAVE MADE THE LIGHTS APPEAR BE ILLUMINATED GREEN. ADDITIONALLY, THE STUDENT AND FLIGHT INSTRUCTOR HAVE INDICATED THAT THE GEAR HORN DID NOT SOUND AS DESIGNED. ## Other reports on N6698F (4) Matched to the same aircraft by N-number and date. - [Incident 20150511007339I](https://openairdocs.org/incident/20150511007339I), May 11, 2015: Beech C24R (N6698F), Riverside, CA, No damage. While performing touch and goes, pilot declared an emergency with engine failure while on left downwind for rwy 27. Cleared to land on any rwy. Subsequently… - [Incident 20090111000309I](https://openairdocs.org/incident/20090111000309I), Jan 11, 2009: Beech C24R (N6698F), Chino, CA, Minor damage. (-23) N6698F a Beechcraft BE-24 was in the traffic pattern to land on rwy 3, cno airport. The aircraft landed gear up. The pilot was the sole occupant with no… - [Incident 19990320037949I](https://openairdocs.org/incident/19990320037949I), Mar 20, 1999: Beech C24R (N6698F), Leesburg, FL, Minor damage. (-23) Pilot (vitale) stated to inspector kimbah he forgot to put gear down. Mechanic, 1st on scene, stated gear lever was in up position when he got to… - [Incident 19811030079759I](https://openairdocs.org/incident/19811030079759I), Oct 30, 1981: Beech C24R (N6698F), San Luis Obisbo, CA, Minor damage. Pilot veered off runway shortly after touchdown. Unable to return to runway. 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.