Narrative:

I was the captain on a flight to cedar rapids (cid). We departed on runway 32 and received the EFIS comp mon message, which is a very common message to receive when departing from runway 32. Once we retracted the landing gear and flaps, we put the autoplt on and adjusted the captain's directional gyroscope by pushing the slew toggle switch on the compass control panel. We received the message a few more times during the flight and each time we cleared the message by adjusting the directional gyroscope's heading. I called maintenance control to discuss the observations and made an entry in the logbook. Once on the ground, the first officer and I realized that I never called for the QRH to address the EFIS comp mon message. Supplemental information from acn 583184: this message alerts the crew to a directional mis-alignment between the FMS and the compass heading. On climb out we received the same message as well as on the descent (primarily during the critical phase of flight below 10000 ft) for the visual approach on runway 9 into cid. I tried to adjust the deviation to determine the side the deviation was coming from (ie, PF or PNF), but was not able to make a clear determination due to the time constraints of the visual approach. Furthering our issue to deal with the EFIS comp message properly was the early turn onto base leg by cid approach along with an unusual high airspeed assignment of 210 KTS. By the time I had asked for a speed reduction and received visual approach clearance, completed setting the flaps and running the landing checklist, I noticed that at approximately 700 ft AGL we had passed through the localizer and received a GPWS 'GS' aural warning. The captain (PF) managed to stabilize the approach at 500 ft AGL, as required by our company fom for a visual approach. In retrospect, we never did call for the QRH in-flight.

Related reports:

Google
 

Original NASA ASRS Text

Title: A CL65 FLT CREW WAS ABLE TO STABILIZE THEIR APCH IN TIME FOR A SAFE APCH AND LNDG AFTER HAVING A PROB WITH THE HEADING COMPATIBILITY BTWN THE FMS AND THE COMPASS HEADING DURING A VISUAL APCH. ONCE ON THE GND CREW REALIZED THEY HAD NOT REFERRED TO THE CHKLIST FOR THE ACFT EQUIP PROB GOING INTO CID, IA.

Narrative: I WAS THE CAPT ON A FLT TO CEDAR RAPIDS (CID). WE DEPARTED ON RWY 32 AND RECEIVED THE EFIS COMP MON MESSAGE, WHICH IS A VERY COMMON MESSAGE TO RECEIVE WHEN DEPARTING FROM RWY 32. ONCE WE RETRACTED THE LNDG GEAR AND FLAPS, WE PUT THE AUTOPLT ON AND ADJUSTED THE CAPT'S DIRECTIONAL GYROSCOPE BY PUSHING THE SLEW TOGGLE SWITCH ON THE COMPASS CTL PANEL. WE RECEIVED THE MESSAGE A FEW MORE TIMES DURING THE FLT AND EACH TIME WE CLRED THE MESSAGE BY ADJUSTING THE DIRECTIONAL GYROSCOPE'S HEADING. I CALLED MAINT CTL TO DISCUSS THE OBSERVATIONS AND MADE AN ENTRY IN THE LOGBOOK. ONCE ON THE GND, THE FO AND I REALIZED THAT I NEVER CALLED FOR THE QRH TO ADDRESS THE EFIS COMP MON MESSAGE. SUPPLEMENTAL INFO FROM ACN 583184: THIS MESSAGE ALERTS THE CREW TO A DIRECTIONAL MIS-ALIGNMENT BTWN THE FMS AND THE COMPASS HEADING. ON CLBOUT WE RECEIVED THE SAME MESSAGE AS WELL AS ON THE DSCNT (PRIMARILY DURING THE CRITICAL PHASE OF FLT BELOW 10000 FT) FOR THE VISUAL APCH ON RWY 9 INTO CID. I TRIED TO ADJUST THE DEV TO DETERMINE THE SIDE THE DEV WAS COMING FROM (IE, PF OR PNF), BUT WAS NOT ABLE TO MAKE A CLR DETERMINATION DUE TO THE TIME CONSTRAINTS OF THE VISUAL APCH. FURTHERING OUR ISSUE TO DEAL WITH THE EFIS COMP MESSAGE PROPERLY WAS THE EARLY TURN ONTO BASE LEG BY CID APCH ALONG WITH AN UNUSUAL HIGH AIRSPD ASSIGNMENT OF 210 KTS. BY THE TIME I HAD ASKED FOR A SPD REDUCTION AND RECEIVED VISUAL APCH CLRNC, COMPLETED SETTING THE FLAPS AND RUNNING THE LNDG CHKLIST, I NOTICED THAT AT APPROX 700 FT AGL WE HAD PASSED THROUGH THE LOC AND RECEIVED A GPWS 'GS' AURAL WARNING. THE CAPT (PF) MANAGED TO STABILIZE THE APCH AT 500 FT AGL, AS REQUIRED BY OUR COMPANY FOM FOR A VISUAL APCH. IN RETROSPECT, WE NEVER DID CALL FOR THE QRH INFLT.

Data retrieved from NASA's ASRS site as of July 2007 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.