B737-800 CREW HAD TRACK DEV AT RJBB.

Date: 2002-01 · Aircraft: B737-800 · Phase: approach

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-weather-turbulence|other-fms-operting-protocol-and-sop-crew-concept|crm

Synopsis

B737-800 CREW HAD TRACK DEV AT RJBB.

Narrative

KIX ILS 24 MAYAH. OFF COURSE AFTER MAYAH. WE DID NOT SELECT MAYAH TRANSITION; BEGAN TO FLY FROM MAYAH TO KN DIRECT; S OF COURSE. ATC SAW ERROR AND VECTORED US TO MAYAH FOR ANOTHER APCH. I ADDED TO AND PROBABLY INTERRUPTED THE PF'S BRIEF. WE DID NOT CHK THE LEGS PAGE (THEY ARE USUALLY CORRECT). I TALKED ABOUT MANDATORY ALTS; THE NEED TO BE SLOW AT MAYAH; NOT TO GO DOWN AND SLOW DOWN AT SAME TIME BECAUSE 2000 FT WAS MANDATORY ALSO. I POINTED OUT ALL THE OTHER ALTS AND RESTRS; TOLD OF PROBS WITH THIS APCH WITH B757 AND B727. I CONSIDERED MYSELF AN EXPERT; HAVING FLOWN THIS APCH SO MANY TIMES. WITH THIS EXTRA AND UNNECESSARY BRIEF; I OVERLOOKED THE BASICS AND CAUSED MY FO TO OVERLOOK THEM IN HIS BRIEF AND SET-UP. SUPPLEMENTAL INFO FROM ACN 535462: AUTOPLT FLEW FROM MAYAH INTXN TO LOM BECAUSE OF FMS PROGRAMMING ERROR. I (PF) DID NOT INCLUDE MAYAH TRANSITION AS PART OF FMS LEAD-IN TO RWY 24 LOC/GS. ACFT FLEW FROM FMS IAF MAYAH TO KN LOM WITHOUT FLYING MAYAH TRANSITION. PF (MYSELF) DID NOT PROPERLY PROGRAM CDU TO FLY TRANSITION. OUR FREQUENT ENTRY INTO THIS ARPT MAY HAVE CONTRIBUTED TO A SENSE OF COMPLACENCY. I KNOW IT DID ON MY PART (PF).

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.