37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 909325 |
Time | |
Date | 201009 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Flight Plan | IFR |
Person 1 | |
Function | Dispatcher |
Qualification | Dispatch Dispatcher |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural FAR |
Narrative:
I had submitted a release to the station but did not do it right and did not have takeoff data ready. My lead attempted to help me do this release because it involved drift down analysis and special attention to detail due to the nature of the flight over mountainous terrain which is not generally where we operate. I finished the release and then tried to call the station to have them pull a new release and give the pilot the proper information. I called 15 times and no answer. I had to call shift supervisor for ATC center just to get the ATC tower phone number. Called them and asked them to please have crew call dispatch. They complied and said they would. Twenty minutes before the flight was due to depart; the captain called me and said they did not have takeoff data and I said yes I know. I also said you have all the wrong numbers on the release and could you please have the station call me. He said yes and so departure time came and no call. The flight departed 40 minutes late and no call even after more phone calls by me. The flight shows out on time and that is bull and I know it because the captain told me on a phone patch that they were over weight per the release and weights that were figured out. It was brought to my attention that the driftdown analysis required for this flight was missing from the flight release. This was my first time dispatching a flight that required driftdown data and I had the escape route data for loss of pressurization confused with the driftdown data. I believe in my experience that anytime something new is implemented in our dispatch department; only the minimal amount of training is given. If I am responsible for my flights and held accountable for my flights as a certificated dispatcher than all of us should be trained on everything and not just the leads. Our training instructor is an excellent instructor and is very patient but it seems as if she is only given criteria from higher ups and a time limit to train dispatchers. We all need to know all newly implemented procedures back and front so that we can dispatch our respective flights without incident. We do not have ACARS. I think that is a big problem due to the nature of the business but hey how many times have we said something about it. During flight operations; there should be someone in operations at all times to man the phones and desk. Since we do not have ACARS; it is a problem that needs to be addressed. This miscommunication could have resulted in death and injury but nobody seems to care.
Original NASA ASRS Text
Title: Air Carrier Dispatcher laments the lack of training when new procedures are implemented. He also believes that ACARS is an essential tool for communicating directly with the flight crew; which his company does not use.
Narrative: I had submitted a release to the station but did not do it right and did not have takeoff data ready. My Lead attempted to help me do this release because it involved drift down analysis and special attention to detail due to the nature of the flight over mountainous terrain which is not generally where we operate. I finished the release and then tried to call the station to have them pull a new release and give the pilot the proper information. I called 15 times and no answer. I had to call Shift Supervisor for ATC Center just to get the ATC Tower phone number. Called them and asked them to please have crew call Dispatch. They complied and said they would. Twenty minutes before the flight was due to depart; the Captain called me and said they did not have takeoff data and I said yes I know. I also said you have all the wrong numbers on the release and could you please have the station call me. He said yes and so departure time came and no call. The flight departed 40 minutes late and no call even after more phone calls by me. The flight shows out on time and that is bull and I know it because the Captain told me on a phone patch that they were over weight per the release and weights that were figured out. It was brought to my attention that the driftdown analysis required for this flight was missing from the flight release. This was my first time dispatching a flight that required driftdown data and I had the escape route data for loss of pressurization confused with the driftdown data. I believe in my experience that anytime something new is implemented in our Dispatch Department; only the minimal amount of training is given. If I am responsible for my flights and held accountable for my flights as a certificated dispatcher than all of us should be trained on everything and not just the Leads. Our training instructor is an excellent instructor and is very patient but it seems as if she is only given criteria from higher ups and a time limit to train dispatchers. We all need to know all newly implemented procedures back and front so that we can dispatch our respective flights without incident. We do not have ACARS. I think that is a big problem due to the nature of the business but hey how many times have we said something about it. During flight operations; there should be someone in Operations at all times to man the phones and desk. Since we do not have ACARS; it is a problem that needs to be addressed. This miscommunication could have resulted in death and injury but nobody seems to care.
Data retrieved from NASA's ASRS site as of April 2012 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.