A11 CTLR DESCRIBED CONFLICT WITH MIL ACFT LNDG ELMENDORF AFB AND DEPARTING ANC AT 2500 FT; NO RECORDED LOSS OF SEPARATION LISTED.

Date: 2006-04 · Aircraft: Eagle (F-15) · Phase: descent

Anomalies: deviation-discrepancy-procedural-published-material-policy

Synopsis

A11 CTLR DESCRIBED CONFLICT WITH MIL ACFT LNDG ELMENDORF AFB AND DEPARTING ANC AT 2500 FT; NO RECORDED LOSS OF SEPARATION LISTED.

Narrative

I WAS WORKING N RADAR; HANDLING DEPS AND ARRS OFF ANC ARPT AND ELMENDORF AFB. I HAD A HDOF TO ASSIST ME WHO WAS TRAINING A DEVELOPMENTAL. WE WERE IN THE MIDST OF A LARGE ARR RUSH OF FIGHTERS TO ELMENDORF. THE FINAL TO ELMENDORF CROSSES JUST OFF THE DEP END OF RWY 32 AT ANCHORAGE. ANCHORAGE TWR CALLS HDOF FOR DEP RELEASES. HDOF WAS MAKING GOOD RELEASES BTWN THE FLTS OF FIGHTERS. IT GOT DRAMATICALLY MORE COMPLEX AS THE FLTS OF FIGHTERS BEGAN REQUESTING FLT SPLIT-UPS FOR INDIVIDUAL PAR'S. THEN IT GOT EVEN MORE COMPLEX WHEN EDF GCA ADVISED THEY WANTED 10-12 MI BTWN ACFT ON THEIR RWY 6 FINAL. I WAS SCRAMBLING TO SPLIT UP FLTS AND KEEP THEM AT THE REQUIRED INTERVAL AND NOT DEVIATE S RADAR'S AIRSPACE. ANC TWR IS VERY BAD AT 'HITTING HOLES' ON THE ELMENDORF FINAL WITH RWY 32 DEPS. 10 MI GAPS ARE JUST BIG ENOUGH. I HAD ACFT X ON A 070 DEG HDG DSNDING TO 1600 FT ON A 12 MI FINAL TO ELMENDORF. I SAW THE SPACING WAS GOOD WITH ACFT X PRECEDING TFC; SO I SWITCHED HIM TO THE GCA; FORGETTING THERE WAS 1 XING DEP OFF RWY 32 IN FRONT OF HIM. ACFT Y DEPARTED; I IDENTED HIM AND TURNED HIM TO A 360 DEG HDG TO GET ACROSS ACFT X FINAL SOONER. I ISSUED TFC TO ACFT Y WHO GOT THE FIGHTER IN SIGHT WHEN THEY WERE ABOUT 4 MI APART; AND I INSTRUCTED HIM TO MAINTAIN VISUAL SEPARATION. CONCURRENTLY; HDOF CALLED GCA TO ISSUE TFC TO ACFT X AND ADVISE HIM TO MAINTAIN VISUAL SEPARATION. I SCREWED UP. I FORGOT THE HVY DEP AND GAVE THE COM CHANGE TO ACFT X TOO SOON AND SCREWED MYSELF. TFC WAS WAY TOO FAST AND COMPLEX AND I SIMPLY LOST TRACK OF THE ANC DEPS. HDOF WAS TRAINING AND COORDINATING WHEN I COM-CHANGED SO THEY DID NOT CATCH THAT. ANOTHER BAD DAY.

More incidents for this aircraft family →

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