Date: 201406
Local time of day: 0001-0600
Location: ZZZ.TRACON, US
Aircraft: Q400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Flight Director
Component problem: Failed; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: On initial climbout; we lost both flight directors after the Captain used the TCS button and was not able to regain guidance using the various modes on the FGCP.  After reaching 10;000 FT MSL; I referenced the checklist for an appropriate checklist to complete.  I referenced the avionics chapter; specifically looking for references to the Flight Director; but none of the checklists seemed to fit our situation.  I also looked for a checklist referring to the TCS; but again nothing seemed appropriate.  We discussed the situation and decided to request a block altitude from ATC for cruise; which we were granted.  We also notified ATC of our situation.  As the pilot monitoring; I notified Dispatch and Maintenance Control of our situation.  Upon reaching cruise altitude; I scanned the Master Index in the checklist to make sure that I had not missed an appropriate checklist.    As we became established on the RNAV arrival; the Controller asked us if we would be able to fly it without the Flight Director.  We quickly discussed the required lateral containment of 1 NM either side of course and responded yes; we could continue with the arrival.  I then referenced the FOM for any guidance on our situation. I found a reference to RNAV SIDs and STARs - Flight Director that states:  'RNAV-1 SIDS require the use of the Flight Director.'  I perceived this as excluding RNAV-1 STARS and felt our position was justified.  We completed the flight without incident.  I later looked at the MEL 34-60-1 FLIGHT DIRECTORS which states 'do not conduct RNAV STARS.'  I feel that we may have inappropriately continued an RNAV arrival without the required equipment.  After the flight; I also did a search on my iPad in the Abnormal Checklist using the term 'flight director' and came up with the checklist 'AFCS Controller Inop (PFD)'.  This seems like it may have been the most appropriate checklist for the situation.  It does say that RNAV STARS are not authorized. Once I found the section in the FOM which seemed applicable to our situation; I believed that we were not prohibited from flying the RNAV STAR in our situation.  A contributing factor was our workload at this point; we were just beginning the descent and I only scanned this page until I found what I was looking for. On this same page under ATC Radar Vectoring; the prohibition on flying RNAV-1 STAR's is alluded to.  Had I taken the time to read this in detail; I would have noticed this.  Given my perceived time constraints; I only scanned the page for what I could recognize as pertinent.  The question of radar vectors was not an immediate concern.  Upon subsequent cross reference with the MEL; I now believe we were wrong to accept this RNAV STAR.


Second narrative: During takeoff I rotated normally to 10 degrees. As we continued our departure I pressed the TCS button on my yoke and continued pitching up to 15 degrees; where I released the TCS button. At this time the Flight Director Command Bars failed to reappear. The reason for this report is; that after landing my First Officer called me to let me know that he'd been able to find some information that we were unable to find while enroute. Firstly; after clearing the airport traffic area and in a sustained climb the First Officer checked the Abnormal Checklist to see what; if any; checklist we should run. He could not find anything to address our issue in the Abnormal book. After we were above 10;000 feet he looked on his iPad in the QRH to see if there were any limitations for flying without a FD; and could not find anything. He then went onto check the FOM; but was not able to readily find any guidance. As a precaution against an altitude deviation we requested a block altitude of 23;000 to 24;000 feet. We continued without incident; or so we thought. It was sometime after we landed that my First Officer was able to inform me that he'd found some information in the FOM that did address our issue; but not anywhere where we have looked. FOM addresses the loss of FD and what limitations it imposes (not in the Abnormal where we would expect to find it). As a result we violated company procedures in continuing on the RNAV ARRIVAL; which is an RNAV-1 arrival and requires the FD. As I recall my First Officer found this in a round about way by a reference in MEL 34-60-1. We inadvertently violated both FAR and company procedures; with the help of not being able to find the needed information in the place we have been trained to expect it to be; i.e.; the Abnormal book.


Synopsis: Q400 flight crew experiences a Flight Director failure on departure and cannot find any direction in the FOM or Abnormal Checklist. After accepting and flying an RNAV arrival it is determined that perhaps they should not have.