37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 626173 |
Time | |
Date | 200408 |
Day | Mon |
Local Time Of Day | 0001 To 0600 |
Place | |
Locale Reference | atc facility : pct.tracon |
State Reference | VA |
Environment | |
Flight Conditions | Marginal |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zau.artcc tracon : pct.tracon tower : iad.tower |
Operator | common carrier : air carrier |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other other vortac |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 8000 flight time type : 3000 |
ASRS Report | 626173 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | inflight encounter : weather non adherence : company policies |
Independent Detector | other flight crewa |
Resolutory Action | controller : separated traffic controller : issued new clearance flight crew : exited adverse environment flight crew : executed missed approach flight crew : diverted to another airport |
Supplementary | |
Problem Areas | Weather Company |
Primary Problem | Weather |
Narrative:
Without prior warning, we were issued holding over bvt at FL370. ZAU asked for our endurance in the hold and we replied it would be only 30 mins, not the 45 mins until our efc. He then gave us delaying vectors and replied to our query of how much longer it would be by saying ZOB and ZID were not going to accept iad bound traffic. Dispatch suggested we proceed to mdt and attempt to refile to iad once closer. We declared mdt as our destination and without having to request it, ATC gave us an mdt clearance, followed almost immediately with a reclrnc to iad. Even after the long delay en route, planned touchdown fuel at iad was 9.0 pounds (original flight plan fuel release 3 showed landing with 13.0 pounds). Potomac approach continued giving delaying vectors throughout our approach. We were given 170 KIAS until the marker of runway 19L. At some point, someone on the approach frequency asked why they were only shooting approachs on runway 19L and the controller responded that there was a disabled aircraft on runway 19R. Flying the assigned speed seemed to put us too close to the traffic ahead, so we began to slow and then the controller asked us to go to target speed (we were already approaching the slowest possible speed). The previous traffic disappeared from our TCASII display and the local controller asked if we had it visually. We could not see the runway or traffic. Tower gave us a missed approach clearance and the first officer (PNF) accepted and declared minimum fuel per our previous decision. Approach was also informed of our fuel and we were vectored to come in on the approach after all other traffic. We were discussing forcing the controller's turn onto final as he turned us in. This time, a different local controller cleared us to land and we specifically requested to confirm adequate spacing on the traffic ahead. ATC confirmed he had spacing and then proceeded to clear a DC9 onto the runway for takeoff when we were inside a 2 mi final. We touched down and after going to idle reverse, got a low fuel EICAS. We blocked with 4.3 pounds after initiating the miss at almost 7.0 pounds on the fuel. Dispatch had not been informed of the disabled aircraft on runway 19R, nor had we, nor had our ATC coordinators at ord. Why?
Original NASA ASRS Text
Title: ENRTE B757-200 IS IMPACTED BY WX, CAUSING AN ALTERNATE REROUTE, THEN REROUTE BACK TO IAD, ORIGINAL DEST. ATC INITIATED MAP RESULTS IN LOW FUEL EICAS ON LNDG. PIC QUESTIONS INTRA COMPANY COORD ALERTING DELAYS ABOUT IAD RWY CLOSURE.
Narrative: WITHOUT PRIOR WARNING, WE WERE ISSUED HOLDING OVER BVT AT FL370. ZAU ASKED FOR OUR ENDURANCE IN THE HOLD AND WE REPLIED IT WOULD BE ONLY 30 MINS, NOT THE 45 MINS UNTIL OUR EFC. HE THEN GAVE US DELAYING VECTORS AND REPLIED TO OUR QUERY OF HOW MUCH LONGER IT WOULD BE BY SAYING ZOB AND ZID WERE NOT GOING TO ACCEPT IAD BOUND TFC. DISPATCH SUGGESTED WE PROCEED TO MDT AND ATTEMPT TO REFILE TO IAD ONCE CLOSER. WE DECLARED MDT AS OUR DEST AND WITHOUT HAVING TO REQUEST IT, ATC GAVE US AN MDT CLRNC, FOLLOWED ALMOST IMMEDIATELY WITH A RECLRNC TO IAD. EVEN AFTER THE LONG DELAY ENRTE, PLANNED TOUCHDOWN FUEL AT IAD WAS 9.0 LBS (ORIGINAL FLT PLAN FUEL RELEASE 3 SHOWED LNDG WITH 13.0 LBS). POTOMAC APCH CONTINUED GIVING DELAYING VECTORS THROUGHOUT OUR APCH. WE WERE GIVEN 170 KIAS UNTIL THE MARKER OF RWY 19L. AT SOME POINT, SOMEONE ON THE APCH FREQ ASKED WHY THEY WERE ONLY SHOOTING APCHS ON RWY 19L AND THE CTLR RESPONDED THAT THERE WAS A DISABLED ACFT ON RWY 19R. FLYING THE ASSIGNED SPD SEEMED TO PUT US TOO CLOSE TO THE TFC AHEAD, SO WE BEGAN TO SLOW AND THEN THE CTLR ASKED US TO GO TO TARGET SPD (WE WERE ALREADY APCHING THE SLOWEST POSSIBLE SPD). THE PREVIOUS TFC DISAPPEARED FROM OUR TCASII DISPLAY AND THE LCL CTLR ASKED IF WE HAD IT VISUALLY. WE COULD NOT SEE THE RWY OR TFC. TWR GAVE US A MISSED APCH CLRNC AND THE FO (PNF) ACCEPTED AND DECLARED MINIMUM FUEL PER OUR PREVIOUS DECISION. APCH WAS ALSO INFORMED OF OUR FUEL AND WE WERE VECTORED TO COME IN ON THE APCH AFTER ALL OTHER TFC. WE WERE DISCUSSING FORCING THE CTLR'S TURN ONTO FINAL AS HE TURNED US IN. THIS TIME, A DIFFERENT LCL CTLR CLRED US TO LAND AND WE SPECIFICALLY REQUESTED TO CONFIRM ADEQUATE SPACING ON THE TFC AHEAD. ATC CONFIRMED HE HAD SPACING AND THEN PROCEEDED TO CLR A DC9 ONTO THE RWY FOR TKOF WHEN WE WERE INSIDE A 2 MI FINAL. WE TOUCHED DOWN AND AFTER GOING TO IDLE REVERSE, GOT A LOW FUEL EICAS. WE BLOCKED WITH 4.3 LBS AFTER INITIATING THE MISS AT ALMOST 7.0 LBS ON THE FUEL. DISPATCH HAD NOT BEEN INFORMED OF THE DISABLED ACFT ON RWY 19R, NOR HAD WE, NOR HAD OUR ATC COORDINATORS AT ORD. WHY?
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.