37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 795377 |
Time | |
Date | 200807 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : mdw.airport |
State Reference | IL |
Altitude | msl single value : 1500 |
Environment | |
Flight Conditions | VMC |
Weather Elements | Thunderstorm |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : c90.tracon |
Operator | general aviation : corporate |
Make Model Name | Continental (Bombardier) |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff ground : maintenance |
Route In Use | departure : on vectors departure sid : n/s |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : multi engine pilot : atp pilot : instrument |
Experience | flight time last 90 days : 80 flight time total : 8300 flight time type : 550 |
ASRS Report | 795377 |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : clearance other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued alert flight crew : overcame equipment problem flight crew : returned to intended or assigned course |
Supplementary | |
Problem Areas | Flight Crew Human Performance Aircraft |
Primary Problem | Ambiguous |
Narrative:
On preflight and taxi out for takeoff at mdw runway 22L; our headings between EFIS/FMS #1 and #2 were significantly off the true magnetic heading. Captain's heading was more than 30 degrees incorrect; copilot heading information more than 20 degrees incorrect. This was now the second time we have seen this occur at mdw in the last 90 days. The 'EFIS miscompare' cas message would not clear; nor would the heading warning flag prior to takeoff. As per the afm; we manually slaved our headings to 224 degrees on the runway just prior to takeoff. All warning flags and messages cleared and we elected to leave the compass in directional gyro mode until we were airborne. (Having seen this message on the ground before at several locations; we knew it was probably ground interference causing the magnetic disruptions and playing havoc with our EFIS heading system.) takeoff roll was normal and initial climb uneventful. Just prior to starting our right turn from 220 degrees around to an initial heading of 110 degrees as part of our vector on the midway 6 departure; I de-selected directional gyro mode. Everything initially looked back to normal and I began my climbing right turn. As I established us in a climbing right 30 degree bank; my heading display on pfd #1 started spinning like a top for a brief second or two. An 'EFIS miscompare' message immediately triggered an amber cas message along with both 'heading' flags on both pfd #1 and #2. I quickly noticed that my heading was now more than 180 degrees in error; and it looked like the copilot's magnetic heading indication was initially correct. I leveled the wings and shallowed off our climb and asked my co-captain to take control while I troubleshot the problem. Chicago departure at the moment asked us 'where are you going;' because we were now headed southwest instead of out towards lewke; almost an east heading from midway. We quickly started back towards the east; while avoiding some thunderstorms in the area; and told departure we were having compass indication problems and were trying to figure it out. We rolled out on about a 060 degree heading and let the magnetic compass stabilize. I turned off the windshield heaters as per afm and reengaged directional gyro mode on the captain's pfd and manually set my heading. ATC then asked what heading we were currently on; I said 'about 060 degrees.' he agreed and then handed us off to ZAU for further handling. I then took back control of the aircraft and had my co-captain manually slave his compass heading on pfd #2. After leveling off at 14000 ft MSL and stabilized for several mins; we de-selected directional gyro mode; back to EFIS; and everything from that point was normal and uneventful. ATC never gave us any indications of a traffic conflict or associated problems from the compass error. In hindsight; I should have waited until we were established on our 110 degree heading in straight in level; unaccelerated flight prior to de-selecting directional gyro mode. There is no immediate reason for going back to EFIS heading without being established first. Lesson learned; and I was just lucky I did not cause a traffic conflict in such a congested area as chicago.
Original NASA ASRS Text
Title: CL30 CAPT REPORTS SIGNIFICANT HEADING DISCREPANCIES BETWEEN HEADING SYSTEMS IN HIS ACFT DURING TAXI OUT. ONCE AIRBORNE PROBLEMS REAPPEAR CAUSING TRACK DEV.
Narrative: ON PREFLT AND TAXI OUT FOR TKOF AT MDW RWY 22L; OUR HDGS BTWN EFIS/FMS #1 AND #2 WERE SIGNIFICANTLY OFF THE TRUE MAGNETIC HDG. CAPT'S HDG WAS MORE THAN 30 DEGS INCORRECT; COPLT HDG INFO MORE THAN 20 DEGS INCORRECT. THIS WAS NOW THE SECOND TIME WE HAVE SEEN THIS OCCUR AT MDW IN THE LAST 90 DAYS. THE 'EFIS MISCOMPARE' CAS MESSAGE WOULD NOT CLR; NOR WOULD THE HDG WARNING FLAG PRIOR TO TKOF. AS PER THE AFM; WE MANUALLY SLAVED OUR HDGS TO 224 DEGS ON THE RWY JUST PRIOR TO TKOF. ALL WARNING FLAGS AND MESSAGES CLRED AND WE ELECTED TO LEAVE THE COMPASS IN DIRECTIONAL GYRO MODE UNTIL WE WERE AIRBORNE. (HAVING SEEN THIS MESSAGE ON THE GND BEFORE AT SEVERAL LOCATIONS; WE KNEW IT WAS PROBABLY GND INTERFERENCE CAUSING THE MAGNETIC DISRUPTIONS AND PLAYING HAVOC WITH OUR EFIS HDG SYS.) TKOF ROLL WAS NORMAL AND INITIAL CLB UNEVENTFUL. JUST PRIOR TO STARTING OUR R TURN FROM 220 DEGS AROUND TO AN INITIAL HDG OF 110 DEGS AS PART OF OUR VECTOR ON THE MIDWAY 6 DEP; I DE-SELECTED DIRECTIONAL GYRO MODE. EVERYTHING INITIALLY LOOKED BACK TO NORMAL AND I BEGAN MY CLBING R TURN. AS I ESTABLISHED US IN A CLBING R 30 DEG BANK; MY HDG DISPLAY ON PFD #1 STARTED SPINNING LIKE A TOP FOR A BRIEF SECOND OR TWO. AN 'EFIS MISCOMPARE' MESSAGE IMMEDIATELY TRIGGERED AN AMBER CAS MESSAGE ALONG WITH BOTH 'HDG' FLAGS ON BOTH PFD #1 AND #2. I QUICKLY NOTICED THAT MY HDG WAS NOW MORE THAN 180 DEGS IN ERROR; AND IT LOOKED LIKE THE COPLT'S MAGNETIC HDG INDICATION WAS INITIALLY CORRECT. I LEVELED THE WINGS AND SHALLOWED OFF OUR CLB AND ASKED MY CO-CAPT TO TAKE CTL WHILE I TROUBLESHOT THE PROB. CHICAGO DEP AT THE MOMENT ASKED US 'WHERE ARE YOU GOING;' BECAUSE WE WERE NOW HEADED SW INSTEAD OF OUT TOWARDS LEWKE; ALMOST AN E HDG FROM MIDWAY. WE QUICKLY STARTED BACK TOWARDS THE E; WHILE AVOIDING SOME TSTMS IN THE AREA; AND TOLD DEP WE WERE HAVING COMPASS INDICATION PROBS AND WERE TRYING TO FIGURE IT OUT. WE ROLLED OUT ON ABOUT A 060 DEG HDG AND LET THE MAGNETIC COMPASS STABILIZE. I TURNED OFF THE WINDSHIELD HEATERS AS PER AFM AND REENGAGED DIRECTIONAL GYRO MODE ON THE CAPT'S PFD AND MANUALLY SET MY HDG. ATC THEN ASKED WHAT HDG WE WERE CURRENTLY ON; I SAID 'ABOUT 060 DEGS.' HE AGREED AND THEN HANDED US OFF TO ZAU FOR FURTHER HANDLING. I THEN TOOK BACK CTL OF THE ACFT AND HAD MY CO-CAPT MANUALLY SLAVE HIS COMPASS HDG ON PFD #2. AFTER LEVELING OFF AT 14000 FT MSL AND STABILIZED FOR SEVERAL MINS; WE DE-SELECTED DIRECTIONAL GYRO MODE; BACK TO EFIS; AND EVERYTHING FROM THAT POINT WAS NORMAL AND UNEVENTFUL. ATC NEVER GAVE US ANY INDICATIONS OF A TFC CONFLICT OR ASSOCIATED PROBS FROM THE COMPASS ERROR. IN HINDSIGHT; I SHOULD HAVE WAITED UNTIL WE WERE ESTABLISHED ON OUR 110 DEG HDG IN STRAIGHT IN LEVEL; UNACCELERATED FLT PRIOR TO DE-SELECTING DIRECTIONAL GYRO MODE. THERE IS NO IMMEDIATE REASON FOR GOING BACK TO EFIS HDG WITHOUT BEING ESTABLISHED FIRST. LESSON LEARNED; AND I WAS JUST LUCKY I DID NOT CAUSE A TFC CONFLICT IN SUCH A CONGESTED AREA AS CHICAGO.
Data retrieved from NASA's ASRS site as of May 2009 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.