37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 401480 |
Time | |
Date | 199805 |
Day | Wed |
Local Time Of Day | 0001 To 0600 |
Place | |
Locale Reference | atc facility : atl |
State Reference | GA |
Altitude | msl bound lower : 33000 msl bound upper : 33000 |
Environment | |
Flight Conditions | IMC |
Light | Dawn |
Aircraft 1 | |
Controlling Facilities | artcc : ztl |
Operator | common carrier : air carrier |
Make Model Name | B727 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : flight engineer pilot : cfi |
Experience | flight time last 90 days : 50 flight time total : 5850 flight time type : 370 |
ASRS Report | 401480 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Primary Problem | Weather |
Air Traffic Incident | other |
Narrative:
I reviewed our WX package for flight sdf to jax may/wed/98. Jax was forecast temperature 2 mi 008 broken. We had mco as our only alternate. The problem arose in-flight as I was speaking with our dispatch on the radio (phone patch) and he informed me that our alternate (mco) was forecast 1/2 mi for our time frame. I looked at my WX package again and figured out that we had 2 mco forecasts, I read and underlined (mco) forecast for our time frame of better than 500 ft 1 1/4 mi. I accidentally overlooked the amended forecast which was for 1/2 mi. I think this would have been avoided if our dispatch would only include the most recent forecast on our paperwork. We got a new alternate and we landed at our original destination (jax) uneventfully. I also think my dispatcher for our flight missed the mco forecast (1/2 mi) for the same reason.
Original NASA ASRS Text
Title: B727 ACFT ENRTE TO DEST WHEN RPTR CAPT WAS IN CONTACT WITH HIS COMPANY DISPATCHER WHO INFORMED HIM THAT THE ALT WX FORECAST HAD WORSENED. UPON REVIEWING THE WX PACKAGE ON THE ACFT HE FOUND 2 WX FORECASTS, ONE OUTDATED WHILE THE OTHER WAS CURRENT AND HE HAD NOT SEEN THE LOWER WX. FLC LANDED AT DEST WITHOUT A PROB.
Narrative: I REVIEWED OUR WX PACKAGE FOR FLT SDF TO JAX MAY/WED/98. JAX WAS FORECAST TEMP 2 MI 008 BROKEN. WE HAD MCO AS OUR ONLY ALTERNATE. THE PROB AROSE INFLT AS I WAS SPEAKING WITH OUR DISPATCH ON THE RADIO (PHONE PATCH) AND HE INFORMED ME THAT OUR ALTERNATE (MCO) WAS FORECAST 1/2 MI FOR OUR TIME FRAME. I LOOKED AT MY WX PACKAGE AGAIN AND FIGURED OUT THAT WE HAD 2 MCO FORECASTS, I READ AND UNDERLINED (MCO) FORECAST FOR OUR TIME FRAME OF BETTER THAN 500 FT 1 1/4 MI. I ACCIDENTALLY OVERLOOKED THE AMENDED FORECAST WHICH WAS FOR 1/2 MI. I THINK THIS WOULD HAVE BEEN AVOIDED IF OUR DISPATCH WOULD ONLY INCLUDE THE MOST RECENT FORECAST ON OUR PAPERWORK. WE GOT A NEW ALTERNATE AND WE LANDED AT OUR ORIGINAL DEST (JAX) UNEVENTFULLY. I ALSO THINK MY DISPATCHER FOR OUR FLT MISSED THE MCO FORECAST (1/2 MI) FOR THE SAME REASON.
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.