 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ATCT local controller failed to inform departure control about air carrier X missed approach. Operational deviation.
| Attributes | |
| ACN | 141567 |
| Time | |
| Date | 199003 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : oak |
| State Reference | CA |
| Altitude | msl bound lower : 500 msl bound upper : 500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : oak tower : oak |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
| Flight Phase | descent : approach landing : missed approach |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 230 flight time total : 12000 |
| ASRS Report | 141567 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : non radar |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | controller : issued new clearance |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation |
Narrative:
First officer flying, captain talking. On approach to oak on the ILS at about 2 mi out on final the tower controller stated 'go missed approach.' I stated we were starting the miss and asked what the reason was. He stated there was a plane back taxiing and a plane in position. The tower controller then started talking to an small aircraft. West/O further instruction from the tower we executed the published missed approach instructions. About the time we were cleaned up and established on the missed approach, I asked for a departure frequency. The tower gave us a departure frequency. Departure control was not informed of our miss and it created a conflict with sfo traffic. The reason I believe this occurred was that the tower controller became preoccupied with the small aircraft traffic and neglected to issue us timely missed approach instructions that would have avoided the sfo traffic conflict.
Original NASA ASRS Text
Title: ATCT LCL CTLR FAILED TO INFORM DEP CTL ABOUT ACR X MISSED APCH. OPDEV.
Narrative: F/O FLYING, CAPT TALKING. ON APCH TO OAK ON THE ILS AT ABOUT 2 MI OUT ON FINAL THE TWR CTLR STATED 'GO MISSED APCH.' I STATED WE WERE STARTING THE MISS AND ASKED WHAT THE REASON WAS. HE STATED THERE WAS A PLANE BACK TAXIING AND A PLANE IN POS. THE TWR CTLR THEN STARTED TALKING TO AN SMA. W/O FURTHER INSTRUCTION FROM THE TWR WE EXECUTED THE PUBLISHED MISSED APCH INSTRUCTIONS. ABOUT THE TIME WE WERE CLEANED UP AND ESTABLISHED ON THE MISSED APCH, I ASKED FOR A DEP FREQ. THE TWR GAVE US A DEP FREQ. DEP CTL WAS NOT INFORMED OF OUR MISS AND IT CREATED A CONFLICT WITH SFO TFC. THE REASON I BELIEVE THIS OCCURRED WAS THAT THE TWR CTLR BECAME PREOCCUPIED WITH THE SMA TFC AND NEGLECTED TO ISSUE US TIMELY MISSED APCH INSTRUCTIONS THAT WOULD HAVE AVOIDED THE SFO TFC CONFLICT.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.