Date: 201410
Local time of day: 0601-1200
Location: DFW.Airport, TX
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B DFW
ATC / advisory: TRACON D10
Aircraft component: FMS/FMC
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Human-Machine Interface
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Aircraft Automation Overrode Flight Crew; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: I was assigned the FORCL 1 RNAV DEPARTURE. When loading the RNAV departure the Forck transition did not appear on the FMS; but it did show up on legs page and nav display when reviewed. Upon takeoff the MECHL fix was indicted on nav display in proper order. When climbing out it was Nav Track on the FMA and autopilot on. The Aircraft started a right turn to Mechl fix early; for some reason the fix moved closer to Airport. When I noticed the deviation our altitude was about 2000 feet; and before I could ask for corrective action; the Controller called us and put us on a radar vector to SPIDY fix. No conflict of aircraft at this time. Also I got and RNP indication on the Capt PFD but not on FO PFD; which came on about 15 minutes into flight and stayed on for about 5-10 minutes and went out. Upon continuing flight NAV system was operating OK and all other fixes correct and did not have any further problems with NAV system. We also got a too low warning on Takeoff after about 500 feet. We departed on runway 35L. Note: I called dispatch prior to leaving gate because the flight plan on the FORCL 1 departure showed the South departure fixes even though we departed North. I Think this departure is not correct in the NAV program for North Departure. When problem happened after takeoff and noticed the deviation from what seemed to be a confusing event we should have declared unable RNAV departure and asked Controller for Radar vectors to fixes or track. Further communications with Dispatch about confusion on flight plan and had another Departure filed. I got the same RNAV departure from dispatch on my next flight and called them about the problem I had with the previous flight. This flight also came up with the same South Fixes when we were taking off North. I got refiled by another RNAV departure which showed the appropriate North Fixes on the Flight plan. In talking with dispatch it seem we have a SID that they don't have for some departures for flight planning for specific destinations.


Second narrative: we departed DFW Runway 35L full length on the Forck 1 departure in VMC conditions. Our FMS and Nav displays indicated all the fixes on the departure correctly. For some reason the airplane turned eastbound early (before arriving at Mechl). After checking in with Departure; ATC gave us a radar vectors (northbound) then to Spidy intersection and to resume the departure. The captain's PFD showed a RNP light on during our radar vectors temporarily. However it went away once we were given direct to Spidy intersection and all other Nav and FMS functions worked properly the rest of the flight. When we loaded the Forck1 departure at the gate; the forck transition did not come up. However; when checking the legs page and Nav display; the forck transition was seen. We discussed this at the gate; but saw that the forck intersection showed up on the legs page as well as the Nav displays in the proper sequence. We feel that this could have been a factor in the FMS causing us to turn early possibly. Captain was flying and I was the pilot monitoring. By the time we realized the plane turned early and something was wrong; ATC gave us a heading to correct our course. Avoidance of this problem would have been to have dispatch file us for a different SID which showed the transition after selecting the SID on the FMS; and not accepting a SID in which the FMS didn't display a transition to put in. I feel that my low time in type (60 hours) caused me to not recognize the problem sooner. This all happened while I was doing the climb flow setting the vertical rate; climb power and positioning the flaps up; then taking a radio handoff from tower to departure control. The red flags started at the gate loading the departure in the FMS; and continued at about the time I was doing my after takeoff flow.


Synopsis: MD-83 flight crew experiences a track deviation during the FORCK 1 RNAV departure from Runway 35L at DFW. With the autopilot engaged the aircraft begin a turn to the east prior to reaching MECHL. The early turn is detected by ATC and a vector heading is provided.