37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 786683 |
Time | |
Date | 200805 |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : iad.airport |
State Reference | DC |
Altitude | msl single value : 2000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tower : iad.tower |
Operator | common carrier : air carrier |
Make Model Name | EMB ERJ 170/175 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : takeoff |
Route In Use | departure sid : n/s |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : iad.tower |
Operator | common carrier : air taxi |
Make Model Name | EMB ERJ 145 ER&LR |
Operating Under FAR Part | Part 135 |
Flight Phase | landing : missed approach landing : go around |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : radar controller : military |
Experience | controller limited radar : 3 controller military : 4 controller radar : 23 controller time certified in position1 : 15 |
ASRS Report | 786683 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | conflict : airborne less severe non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance |
Miss Distance | vertical : 1000 |
Supplementary | |
Problem Areas | ATC Human Performance Airspace Structure Airport |
Primary Problem | ATC Human Performance |
Narrative:
Landing runway 19L/right and runway 12 simultaneously using visual approachs while departing runway 19L. An aircraft landing runway 12 rolled long so I had to send the next aircraft landing runway 12 around. In order to miss traffic departing runway 19L; I had to turn the go around to the east to pass behind the departure and I climbed him to 2000 ft. The departure off runway 19L continued climbing straight out (heading 190 degrees) and I used the racd to turn my aircraft right heading 230 degrees behind him. However; due to my workload; I didn't realize that the go around had climbed to 3000 ft when I turned him to 230 degrees. I asked him to verify 2000 ft and he said he thought I climbed him to 4000 ft. By this time I had both aircraft in sight and told mine to maintain 3000 ft. The departure was out of 4000 ft so I gave the go around to departure heading 230 degrees at 3000 ft for re-sequencing to runway 12. 1) technically; I did not have both aircraft in sight at all times although they were on diverging headings when the go around passed over the tower. 2) having worked radar for 23 yrs; it was just second nature to use the racd to vector my go around until I could see him again. However; I missed the busted altitude because I was busy with arrs. 3) the pilot busted his altitude but because it didn't cause a deal; I didn't report a pilot deviation. 4) I know I gave him 2000 ft but I don't know what he read back. 5) even without altitude; I think I had 3 mi separation between the departure and the go around when I turned him to 230 degrees. 6) I called traffic; but was too busy with arrs to get a response from the go around aircraft or to tell him to maintain visual with the departure. 7) in the old tower; I would have been able to keep both aircraft in sight but due to the location of the new tower; I couldn't keep my go around in sight. 8) when the go around aircraft passed behind the departure; I had them both in sight. However; the departure had been shipped to pct departure. Technically; I can only provide visual separation between aircraft under control of the same facility. Therefore; it doesn't matter if I had them both in sight or not.
Original NASA ASRS Text
Title: IAD CTLR DESCRIBED GAR EVENT ON RWY 12; CONFLICTING WITH RWY 19L DEP TFC; INDICATING SEPARATION WAS MAINTAINED BUT NOT ALL RULES FOLLOWED.
Narrative: LNDG RWY 19L/R AND RWY 12 SIMULTANEOUSLY USING VISUAL APCHS WHILE DEPARTING RWY 19L. AN ACFT LNDG RWY 12 ROLLED LONG SO I HAD TO SEND THE NEXT ACFT LNDG RWY 12 AROUND. IN ORDER TO MISS TFC DEPARTING RWY 19L; I HAD TO TURN THE GAR TO THE E TO PASS BEHIND THE DEP AND I CLBED HIM TO 2000 FT. THE DEP OFF RWY 19L CONTINUED CLBING STRAIGHT OUT (HDG 190 DEGS) AND I USED THE RACD TO TURN MY ACFT R HDG 230 DEGS BEHIND HIM. HOWEVER; DUE TO MY WORKLOAD; I DIDN'T REALIZE THAT THE GAR HAD CLBED TO 3000 FT WHEN I TURNED HIM TO 230 DEGS. I ASKED HIM TO VERIFY 2000 FT AND HE SAID HE THOUGHT I CLBED HIM TO 4000 FT. BY THIS TIME I HAD BOTH ACFT IN SIGHT AND TOLD MINE TO MAINTAIN 3000 FT. THE DEP WAS OUT OF 4000 FT SO I GAVE THE GAR TO DEP HDG 230 DEGS AT 3000 FT FOR RE-SEQUENCING TO RWY 12. 1) TECHNICALLY; I DID NOT HAVE BOTH ACFT IN SIGHT AT ALL TIMES ALTHOUGH THEY WERE ON DIVERGING HDGS WHEN THE GAR PASSED OVER THE TWR. 2) HAVING WORKED RADAR FOR 23 YRS; IT WAS JUST SECOND NATURE TO USE THE RACD TO VECTOR MY GAR UNTIL I COULD SEE HIM AGAIN. HOWEVER; I MISSED THE BUSTED ALT BECAUSE I WAS BUSY WITH ARRS. 3) THE PLT BUSTED HIS ALT BUT BECAUSE IT DIDN'T CAUSE A DEAL; I DIDN'T RPT A PLTDEV. 4) I KNOW I GAVE HIM 2000 FT BUT I DON'T KNOW WHAT HE READ BACK. 5) EVEN WITHOUT ALT; I THINK I HAD 3 MI SEPARATION BTWN THE DEP AND THE GAR WHEN I TURNED HIM TO 230 DEGS. 6) I CALLED TFC; BUT WAS TOO BUSY WITH ARRS TO GET A RESPONSE FROM THE GAR ACFT OR TO TELL HIM TO MAINTAIN VISUAL WITH THE DEP. 7) IN THE OLD TWR; I WOULD HAVE BEEN ABLE TO KEEP BOTH ACFT IN SIGHT BUT DUE TO THE LOCATION OF THE NEW TWR; I COULDN'T KEEP MY GAR IN SIGHT. 8) WHEN THE GAR ACFT PASSED BEHIND THE DEP; I HAD THEM BOTH IN SIGHT. HOWEVER; THE DEP HAD BEEN SHIPPED TO PCT DEP. TECHNICALLY; I CAN ONLY PROVIDE VISUAL SEPARATION BTWN ACFT UNDER CTL OF THE SAME FACILITY. THEREFORE; IT DOESN'T MATTER IF I HAD THEM BOTH IN SIGHT OR NOT.
Data retrieved from NASA's ASRS site as of May 2009 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.