37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 380696 |
Time | |
Date | 199709 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : mxe |
State Reference | PA |
Altitude | msl bound lower : 10000 msl bound upper : 10000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zny tracon : phl |
Operator | common carrier : air carrier |
Make Model Name | B737-500 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | departure other enroute : direct enroute : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737-500 |
Operating Under FAR Part | Part 121 |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : commercial pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 19000 flight time type : 14000 |
ASRS Report | 380696 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : flight engineer pilot : commercial |
Experience | flight time last 90 days : 240 flight time total : 12500 flight time type : 8000 |
ASRS Report | 380237 |
Events | |
Anomaly | other anomaly other |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : issued new clearance |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Inter Facility Coordination Failure |
Situations | |
ATC Facility | procedure or policy : unspecified |
Narrative:
Level at 10000 ft after normal takeoff from phl. Proceeding direct to mxe VOR, approaching mxe, departure control advised that she was unable to make a handoff to ZNY and that we should turn to heading 090 degrees and maintain 10000 ft. I questioned left or right turn twice and finally was told left turn to heading 090 degrees (we were heading approximately 270 degrees at the time). At approximately 120 degree heading, we were cleared directly to mxe VOR to hold 'west as published -- efc AB45.' the closest way back to mxe was a right turn which we made because of no more instructions. Apparently the controller assumed we would turn left to mxe because she questioned our direction of turn. She accepted our explanation as we were less than 8 mi from mxe. Because of other traffic the controller was constantly busy. After checking all high and low maps I could not find a published holding pattern at mxe. Prior to reaching mxe, departure control advised us to maintain our heading to intercept the mxe 278 degree radial and then proceed flight plan route. I questioned if the handoff was made and she confirmed it was. We were switched to ZNY where the controller advised that the entire problem was caused by a program called 'dulles high' concerning international arrs at iad. There were no violations -- just mass confusion on ATC's and our part. ATC was very busy and we were busy. I will advise the ATC department of my company of the 'dulles high' program to see if any changes can be made. I think that departure rtes should be modified from phl to avoid this problem.
Original NASA ASRS Text
Title: DEP ACR B737-500 GIVEN DELAY VECTORS WHEN THE DEP CTLR AT PHL IS UNABLE TO EFFECT A HDOF TO ZNY. RPTR CITES CONFUSION DUE TO HDOF DELAYS WITH HIGH WORKLOADS ON ATC AND FLC. RPTR WAS TOLD THAT THE 'DULLES HIGH ARRS' PROC WAS THE CULPRIT.
Narrative: LEVEL AT 10000 FT AFTER NORMAL TKOF FROM PHL. PROCEEDING DIRECT TO MXE VOR, APCHING MXE, DEP CTL ADVISED THAT SHE WAS UNABLE TO MAKE A HDOF TO ZNY AND THAT WE SHOULD TURN TO HDG 090 DEGS AND MAINTAIN 10000 FT. I QUESTIONED L OR R TURN TWICE AND FINALLY WAS TOLD L TURN TO HDG 090 DEGS (WE WERE HDG APPROX 270 DEGS AT THE TIME). AT APPROX 120 DEG HDG, WE WERE CLRED DIRECTLY TO MXE VOR TO HOLD 'W AS PUBLISHED -- EFC AB45.' THE CLOSEST WAY BACK TO MXE WAS A R TURN WHICH WE MADE BECAUSE OF NO MORE INSTRUCTIONS. APPARENTLY THE CTLR ASSUMED WE WOULD TURN L TO MXE BECAUSE SHE QUESTIONED OUR DIRECTION OF TURN. SHE ACCEPTED OUR EXPLANATION AS WE WERE LESS THAN 8 MI FROM MXE. BECAUSE OF OTHER TFC THE CTLR WAS CONSTANTLY BUSY. AFTER CHKING ALL HIGH AND LOW MAPS I COULD NOT FIND A PUBLISHED HOLDING PATTERN AT MXE. PRIOR TO REACHING MXE, DEP CTL ADVISED US TO MAINTAIN OUR HEADING TO INTERCEPT THE MXE 278 DEG RADIAL AND THEN PROCEED FLT PLAN RTE. I QUESTIONED IF THE HDOF WAS MADE AND SHE CONFIRMED IT WAS. WE WERE SWITCHED TO ZNY WHERE THE CTLR ADVISED THAT THE ENTIRE PROB WAS CAUSED BY A PROGRAM CALLED 'DULLES HIGH' CONCERNING INTL ARRS AT IAD. THERE WERE NO VIOLATIONS -- JUST MASS CONFUSION ON ATC'S AND OUR PART. ATC WAS VERY BUSY AND WE WERE BUSY. I WILL ADVISE THE ATC DEPT OF MY COMPANY OF THE 'DULLES HIGH' PROGRAM TO SEE IF ANY CHANGES CAN BE MADE. I THINK THAT DEP RTES SHOULD BE MODIFIED FROM PHL TO AVOID THIS PROB.
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.