37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1411508 |
Time | |
Date | 201612 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Brasilia EMB-120 All Series |
Operating Under FAR Part | Part 135 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Dispatcher |
Qualification | Dispatch Dispatcher |
Experience | Dispatch Dispatch 17 |
Events | |
Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
I had an EMB120 charter flight on my dispatch desk to ZZZ. I had thoroughly looked at the brasilia [performance] data for the takeoff and landing weights for all of the airports involved; including all the alternate airports; as we are required to list alternate airports for our charter flights. I had thoroughly spoke on the phone with our captain well before the flight left to review everything and confirm that the crew had all of the brasilia [performance] data for all of the airports listed on the dispatch release; as some of those airports we no longer serve. I also confirmed she had all of the jeppesen instrument approach charts/plates for all of the airports listed on the dispatch release. So this charter flight took off enroute to ZZZ. During flight; the crew called myself on our company radio requesting the ZZZ landing data; which I verbally gave them over the company radio. I also filled out our company's communication log as required; communicating to flights enroute. I was surprised they asked for this; as I asked if they had it all before takeoff. I had also added many written remarks on the dispatch release; one of which was to take all of the brasilia [performance] data for all of the airports listed on the dispatch release for takeoff and landing. Next; my dispatch manager asked myself if I had sent the ZZZ brasilia data from another source; on a different drive in our dispatch computer system. I had not done this as I did not know there were 2 different sets of brasilia [performance] data for ZZZ. I told him I did not send it to the crew. In our company [performance] manuals for the brasilia; there was already [performance] data for ZZZ; takeoff and landing; so I assumed the crew also had it in their manual as well; since the [performance] revisions are all issued to both dispatch and all the aircraft to be revised and therefore current. So this crew had no ZZZ brasilia [performance] data. My dispatch manager; then e-mailed it for the crew upon their arrival in ZZZ; which they then had. This entire charter flight was a mess from the start. 24 hours before this charter flight; there was no captain assigned to it. The day of the charter flight; the original first officer could not fly it due to FAA duty time problems; so a new first officer was assigned to it; who could legally take the time. A fuel stop was then planned in since this charter flight. Charter flight was released for a ZZZ1 fuel stop only; with all the required alternate airports listed in the dispatch release. In the mess of all this; I did not know there were 2 different sets of ZZZ brasilia [performance] data. I attempted several times to submit a report into our company's safety reporting program. I initially had it all typed in the report and ready to submit it; but it would not submit. Later; I could not even log in to the reports to do one; so I am submitting this instead. I advised both pilots of this situation and told them to submit their own individual safety reports for FAA protection. It has been mentioned several times that the company have electronic manuals; like all the other airlines to avoid all this; but the company refuses to spend the money to do so. All of this would have been avoided; since electronic manuals would automatically be revised; and therefore; current. That would be my suggestion here for this. Our management seems to be indifferent about operations; including charter flights. They are happy about the incoming revenue dollars; but do not care that licensed FAA professionals; pilots and dispatchers; are legally liable for mistakes when they happen.
Original NASA ASRS Text
Title: EMB-120 Dispatcher reported dispatching a charter flight to an off line airport thinking that the necessary performance data was contained in the flight manual. It no longer was and the landing data had to be sent over the radio at the crew's request.
Narrative: I had an EMB120 charter flight on my dispatch desk to ZZZ. I had thoroughly looked at the Brasilia [performance] data for the takeoff and landing weights for all of the airports involved; including all the alternate airports; as we are required to list alternate airports for our charter flights. I had thoroughly spoke on the phone with our captain well before the flight left to review everything and confirm that the crew had all of the Brasilia [performance] data for all of the airports listed on the dispatch release; as some of those airports we no longer serve. I also confirmed she had all of the Jeppesen instrument approach charts/plates for all of the airports listed on the dispatch release. So this charter flight took off enroute to ZZZ. During flight; the crew called myself on our company radio requesting the ZZZ landing data; which I verbally gave them over the company radio. I also filled out our company's communication log as required; communicating to flights enroute. I was surprised they asked for this; as I asked if they had it all before takeoff. I had also added many written remarks on the dispatch release; one of which was to take all of the Brasilia [performance] data for all of the airports listed on the dispatch release for takeoff and landing. Next; my dispatch manager asked myself if I had sent the ZZZ Brasilia data from another source; on a different drive in our dispatch computer system. I had not done this as I did not know there were 2 different sets of Brasilia [performance] data for ZZZ. I told him I did not send it to the crew. In our company [performance] manuals for the Brasilia; there was already [performance] data for ZZZ; takeoff and landing; so I assumed the crew also had it in their manual as well; since the [performance] revisions are all issued to both dispatch and all the aircraft to be revised and therefore current. So this crew had no ZZZ Brasilia [performance] data. My dispatch manager; then e-mailed it for the crew upon their arrival in ZZZ; which they then had. This entire charter flight was a mess from the start. 24 hours before this charter flight; there was no captain assigned to it. The day of the charter flight; the original first officer could not fly it due to FAA duty time problems; so a new first officer was assigned to it; who could legally take the time. A fuel stop was then planned in since this charter flight. Charter flight was released for a ZZZ1 fuel stop only; with all the required alternate airports listed in the dispatch release. In the mess of all this; I did not know there were 2 different sets of ZZZ Brasilia [performance] data. I attempted several times to submit a report into our company's safety reporting program. I initially had it all typed in the report and ready to submit it; but it would not submit. Later; I could not even log in to the reports to do one; so I am submitting this instead. I advised both pilots of this situation and told them to submit their own individual safety reports for FAA protection. It has been mentioned several times that the company have electronic manuals; like all the other airlines to avoid all this; but the company refuses to spend the money to do so. All of this would have been avoided; since electronic manuals would automatically be revised; and therefore; current. That would be my suggestion here for this. Our management seems to be indifferent about operations; including charter flights. They are happy about the incoming revenue dollars; but do not care that licensed FAA professionals; pilots and dispatchers; are legally liable for mistakes when they happen.
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.