Date: 201512
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain
Human factors: Workload; Training / Qualification; Time Pressure; Confusion; Distraction; Human-Machine Interface; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Equipment / Tooling; Company Policy
Primary problem: Company Policy

Narrative: This is not flight specific rather just a general trend I've noticed. I am using the flight from ZZZ-ZZZ1 as a vehicle to input this non-flight specific issue. On a recent work day I flew an aircraft for two legs that due to a deferral required the equipment code filed on the flight plan to be changed. The code was not changed on either leg by the dispatcher so I called the dispatcher and had it changed prior to departure each departure. On one leg I had an FAA individual on the jump seat who happened to be a former dispatcher. We discussed this issue and he told me that since the dispatchers started using [a computer system] as a flight planning tool; the dispatchers work load has increased to the point wherein the dispatchers are spending less time flight monitoring and more time dealing with computer issues. To highlight that; I have the following three examples. The first occurred on the same two flights referenced above wherein the dispatcher changed the equipment code but could not easily get the change displayed on the flight plan I had access to. After about 30 minutes the dispatcher just sent an ACARS message to us indicating the equipment code change sent to the FAA but was unable to display it on our flight plan. The second occurred on the same trip wherein we needed a takeoff alternate due to weather. I phoned the dispatcher to inquire about the alternate and the response was 'Oh. I didn't even look at your departure weather and notice the need for a takeoff alternate.' One was added before departure. The third occurred on a recent flight wherein the ACARS would not return takeoff data to use. We contacted dispatch who sent the needed data with the following response as to the cause of the issue 'No idea why you're getting that message (reference inability to get takeoff data) happens about twice a week to everyone here. Company never has an explanation.'This is meant to bring attention to what appears to be the trend I see in dispatchers missing important flight planning items because of what may be related to other distractions. My concern is how many flights are dispatched with incorrect releases due to this trend I've noticed. These three items above are not the only ones I've seen; they are the most recent thus the only ones I can accurately recollect and document.It appears that further attention may need to be directed to the continuing IT issues.




Synopsis: A Captain reports about deficiencies in the flight planning function of the computer system and its effect on dispatch functionality. The clumsy automation increases workload and decreases effectiveness for dispatch.