37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1276166 |
Time | |
Date | 201507 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | DEN.Airport |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | STAR ANCHR3 |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 248 |
Events | |
Anomaly | Inflight Event / Encounter Fuel Issue Inflight Event / Encounter Weather / Turbulence |
Narrative:
Flight to den was the last leg of a busy three-day trip with the day scheduled for 8:28 block flight time with the final leg scheduled for 2:35 flight time. I was the pilot flying and we departed on time with the legal amount of time left in our day to complete the flight to den; adequate fuel for the route filed; and a very full aircraft. Denver was forecast for the typical pm thunderstorm activity and we had an alternate of abq and cos. [Shortly after takeoff] we were cleared direct to lkt with rest of routing unchanged. After lkt; we were assigned a new arrival; the anchr 3; into den due to thunderstorms. We could deduce by ATC and other airlines that denver arrivals were really being affected by thunderstorms and things were stacking up. Upon passing bff; we were vectored off the arrival and given a southerly heading by a controller who was highly saturated. Then we were turned back north nearly on top of sidney; northeast told to hold there with an efc [25 minutes in the future]. At this point in time; we realized that we were not going to land in denver for possibly another hour and that became concerning. Because of the highly saturated ATC; it was very difficult to communicate in a timely fashion. Our work load increased exponentially within a matter of minutes: navigating the aircraft; communicating with ATC; trying to coordinate dispatch over ACARS; keeping the F/a's and passengers in the loop; as well as communicating with each other. Our fuel quantity was starting to concern us and we had to continually stop and get back into the green rrm. I was tired and feeling a bit concerned about fuel; WX; exceeding duty time; and the possibility of landing at an off station airport. We told the controller that we needed to receive the most direct routing back to den or our fuel could be an issue. They cleared us direct lar (laramie) for the frnch 3 arrival. Along the way; the captain and I discussed our alternate plan and we decided it would be cheyenne; wy; which would be suitable for WX and technically for the 737. Flying all the way to lar would have used quite a bit more fuel and as we flew past the edge of the thunderstorm; I asked the captain to get me direct to a point on the arrival; they gave us skarf and cleared us to fly the arrival. We landed safely and taxied to the gate. I think that as a flight crew we were lulled into complacency by several factors: fatigue; nice WX during the first two legs of the day; poor advanced warning about rapid deteriorating WX in denver both by ATC and dispatch. This caused us to fly away from our destination with our fuel decreasing and our legal flight time timing out; thus limiting our options. In hind sight; I want to be a bit more proactive in communicating and monitoring the developments. When we were assigned direct bff that should have been our cue to contact dispatch about the possibility of heading to our alternate. But complacency can creep up on a flight crew and I was starting to feel the effects of a long trip which accentuates these things. I realize that both ATC and dispatch become task saturated during events like this; however; communicating by ACARS is slow and we need real time WX and communication because it loads up the pilots when we cannot get quicker real time information.
Original NASA ASRS Text
Title: B737 First Officer describes a difficult arrival to DEN due to weather; holding; and fuel considerations.
Narrative: Flight to DEN was the last leg of a busy three-day trip with the day scheduled for 8:28 block flight time with the final leg scheduled for 2:35 flight time. I was the Pilot Flying and we departed on time with the legal amount of time left in our day to complete the flight to DEN; adequate fuel for the route filed; and a very full aircraft. Denver was forecast for the typical PM thunderstorm activity and we had an alternate of ABQ and COS. [Shortly after takeoff] we were cleared direct to LKT with rest of routing unchanged. After LKT; we were assigned a new arrival; the ANCHR 3; into DEN due to thunderstorms. We could deduce by ATC and other airlines that Denver arrivals were really being affected by thunderstorms and things were stacking up. Upon passing BFF; we were vectored off the arrival and given a southerly heading by a Controller who was highly saturated. Then we were turned back north nearly on top of Sidney; NE told to hold there with an EFC [25 minutes in the future]. At this point in time; we realized that we were not going to land in Denver for possibly another hour and that became concerning. Because of the highly saturated ATC; it was very difficult to communicate in a timely fashion. Our work load increased exponentially within a matter of minutes: navigating the aircraft; communicating with ATC; trying to coordinate Dispatch over ACARS; keeping the F/A's and Passengers in the loop; as well as communicating with each other. Our fuel quantity was starting to concern us and we had to continually stop and get back into the green RRM. I was tired and feeling a bit concerned about fuel; WX; exceeding duty time; and the possibility of landing at an off station airport. We told the Controller that we needed to receive the most direct routing back to DEN or our fuel could be an issue. They cleared us direct LAR (Laramie) for the FRNCH 3 Arrival. Along the way; the Captain and I discussed our alternate plan and we decided it would be Cheyenne; WY; which would be suitable for WX and technically for the 737. Flying all the way to LAR would have used quite a bit more fuel and as we flew past the edge of the thunderstorm; I asked the Captain to get me direct to a point on the arrival; they gave us SKARF and cleared us to fly the arrival. We landed safely and taxied to the gate. I think that as a Flight Crew we were lulled into complacency by several factors: fatigue; nice WX during the first two legs of the day; poor advanced warning about rapid deteriorating WX in Denver both by ATC and Dispatch. This caused us to fly away from our destination with our fuel decreasing and our legal flight time timing out; thus limiting our options. In hind sight; I want to be a bit more proactive in communicating and monitoring the developments. When we were assigned direct BFF that should have been our cue to contact Dispatch about the possibility of heading to our alternate. But complacency can creep up on a Flight Crew and I was starting to feel the effects of a long trip which accentuates these things. I realize that both ATC and Dispatch become task saturated during events like this; however; communicating by ACARS is slow and we need real time WX and communication because it loads up the Pilots when we cannot get quicker real time information.
Data retrieved from NASA's ASRS site 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.