ABQ Controller described conflict go-around event on intersecting Runways 17/8; citing new FAA notification requirements for air carrier go-around events; resulting in possible controller reluctance to issue go-arounds creating potential safety issues.

Date: 2009-05 · Aircraft: Any Unknown or Unlisted Aircraft Manufacturer · Phase: landing

Anomalies: atc-issue-all-types|deviation-discrepancy-procedural-published-material-policy

Synopsis

ABQ Controller described conflict go-around event on intersecting Runways 17/8; citing new FAA notification requirements for air carrier go-around events; resulting in possible controller reluctance to issue go-arounds creating potential safety issues.

Narrative

Aircraft X was cleared to land Runway 17 after circling from Runway 8 for an ILS approach. Aircraft Y was cleared to land Runway 26. It was a close situation and one of the aircraft needed to be sent around. BECAUSE OF THE NEW RULES OF THE FAA: IF AN AIRCRAFT GOES AROUND AND IT IS AN AIR CARRIER; A LOG ENTRY IS MADE; TAPES ARE PULLED; THE MANAGER IS CALLED AT HOME; AND THE CONTROLLERS DECISION IS QUESTIONED. Because of this new attitude of the FAA; it makes the controller second guess about sending an aircraft around and which aircraft to be sent around. This attitude sends a dangerous message to controllers and especially to the new hires. It puts aircraft into possible dangerous situations. In the above situation; Aircraft X was sent around at a low attitude. It would have been safer to send around Aircraft Y. But because Aircraft X was sent around instead: No log entry was made; tapes were not pulled; the manager was not called at home; and the controller's judgment was not questioned.

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