37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1291338 |
Time | |
Date | 201508 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | MEM.Airport |
State Reference | TN |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
Per our fom; I reported a cruise altitude change of 4000 ft greater than flight planned to dispatch and never received an acknowledgment that it was received at all. We also had the airport change from a south flow to a north flow and we were not notified; which is not mandatory but certainly nice to know. There are specific items listed in the fom that require notification for change and acknowledgement. This is a constant recurring problem with a lack of support from dispatch while we are enroute which I feel is not in compliance with the intent of flag/domestic operations. Especially with the fuel loads that are on the aircraft with the fuel sense initiative.lack of compliance with far 121 flag domestic operations for 'reliable communications.' I feel our dispatchers handle too many flights at one time and do not have the flight planning system or automation to handle the number we require.better flight planning software to allow point by point updates to our flight plans and more training and compliance from dispatch as true dispatchers rather than flight followers.
Original NASA ASRS Text
Title: B767-300 Captain reported that due to staffing levels he felt he is not supported by Dispatch services to the extent required by FAR 121.
Narrative: Per our FOM; I reported a cruise altitude change of 4000 ft greater than flight planned to Dispatch and never received an acknowledgment that it was received at all. We also had the airport change from a South flow to a North flow and we were not notified; which is not mandatory but certainly nice to know. There are specific items listed in the FOM that require notification for change and acknowledgement. This is a constant recurring problem with a lack of support from Dispatch while we are enroute which I feel is not in compliance with the intent of Flag/Domestic Operations. Especially with the fuel loads that are on the aircraft with the Fuel Sense initiative.Lack of compliance with FAR 121 Flag Domestic Operations for 'reliable communications.' I feel our dispatchers handle too many flights at one time and do not have the Flight Planning System or automation to handle the number we require.Better Flight Planning Software to allow point by point updates to our flight plans and more training and compliance from Dispatch as true Dispatchers rather than flight followers.
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.