37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1329238 |
Time | |
Date | 201601 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ORD.Airport |
State Reference | IL |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Inflight Event / Encounter Fuel Issue |
Narrative:
I am concerned because the dispatch releases are built hours before our flight and the WX can change. It seems at the time the flight release was built it did not require an alternate and none was listed. When we pulled the release with the current WX it did require an alternate. The dispatcher and I did not notice the need for an alternate which concerns me. We are trying to check everyone's job--maintenance etc... And our own job of flying the airplane safely. Distractions can certainly cause us to miss what someone else is supposed to have done. In flight I checked the alternate WX and requested an alternate. We had enough fuel for the sbn alternate per our FMS data. However; a major concern for me was that when I requested performance data--fuel burn etc.--from ord to sbn the flight plan software 'locked up' (dispatcher's words) and was not able to provide us the data.I initially looked at the release and saw there was not an alternate listed. We as the flight crew got distracted with looking at MEL/cdl's to make sure they were correct. We had to do an air start and missed the fact that with the current taf we needed an alternate for our destination. I noticed in cruise after rechecking the WX that we required an alternate. I checked the WX for mke and sbn. I then sent an ACARS to dispatch to add the altitude of sbn. Per my FMS I met the altitude fuel requirements.let all the pilots know that the release may not be correct for altitude WX because they are built (hours) before the flight. However; when the release is pulled it has the latest WX. Check the release for correct landing and alternate minimums. What concerns me is that we have to do everyone's job again. The dispatcher should be monitoring the WX to make the appropriate changes to the release before we as pilots have to. My other major concern is that flight planning software was not able to get flight performance data for the altitude...this issue needs to be addressed immediately.
Original NASA ASRS Text
Title: The Captain; while enroute to ORD; discovered that he had departed without a required alternate airport. Dispatch was unable to provide him with additional required information.
Narrative: I am concerned because the dispatch releases are built hours before our flight and the WX can change. It seems at the time the Flight Release was built it did not require an alternate and none was listed. When we pulled the release with the current WX it did require an alternate. The dispatcher and I did not notice the need for an alternate which concerns me. We are trying to check everyone's job--maintenance etc... and our own job of flying the airplane safely. Distractions can certainly cause us to miss what someone else is supposed to have done. In flight I checked the alternate WX and requested an alternate. We had enough fuel for the SBN alternate per our FMS data. However; a major concern for me was that when I requested performance data--fuel burn etc.--from ORD to SBN the flight plan software 'locked up' (dispatcher's words) and was not able to provide us the data.I initially looked at the release and saw there was not an alternate listed. We as the flight crew got distracted with looking at MEL/CDL's to make sure they were correct. We had to do an air start and missed the fact that with the current TAF we needed an alternate for our destination. I noticed in cruise after rechecking the WX that we required an alternate. I checked the WX for MKE and SBN. I then sent an ACARS to dispatch to add the ALT of SBN. Per my FMS I met the ALT FUEL requirements.Let all the Pilots know that the release may not be correct for ALT WX because they are built (hours) before the flight. However; when the release is pulled it has the latest WX. Check the release for correct Landing and Alternate Minimums. What concerns me is that we have to do everyone's job again. The dispatcher should be monitoring the WX to make the appropriate changes to the Release before we as pilots have to. My other major concern is that flight planning software was not able to get flight performance data for the ALT...This issue needs to be addressed immediately.
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.