37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 595971 |
Time | |
Date | 200309 |
Day | Mon |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : msp.airport |
State Reference | MN |
Altitude | msl single value : 1000 |
Environment | |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : ind.tracon |
Operator | common carrier : air carrier |
Make Model Name | B737-500 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 30r other |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 150 flight time total : 12000 flight time type : 150 |
ASRS Report | 595971 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 16000 flight time type : 2400 |
ASRS Report | 595185 |
Events | |
Anomaly | aircraft equipment problem : critical other anomaly other |
Independent Detector | aircraft equipment : gpws aircraft equipment other aircraft equipment : nav display (nd) other flight crewa other flight crewb |
Resolutory Action | none taken : anomaly accepted |
Consequence | other |
Supplementary | |
Problem Areas | Navigational Facility Aircraft |
Primary Problem | Ambiguous |
Narrative:
I was hand flying a visual approach to runway 30R at msp and noticed a 30 degree map shift on our screens. Knowing the airport extremely well (my neighborhood), I continued the visual using PAPI and raw data. On short final over the river to runway 30R, we had the 'terrain, pull-up-pull-up' commands. Again, I continued my visual slightly above the normal GS with completely visual conditions. I was fully aware of the bogus terrain commands due to the shift of screens showing us well to the south of course. I made a normal landing on runway 30R and we called and made a logbook write-up. Supplemental information from acn 595185: on approach to msp, night VFR, FMC position was off about 10 mi and showed about 30 degrees off heading reference. Bdhi. Cap's navigation panel was on automatic. I shifted to manual and back to automatic. The heading aligned for a few seconds, and then shifted off again.
Original NASA ASRS Text
Title: B737 FLT CREW HAS 'MAP SHIFT' DURING APCH TO MSP.
Narrative: I WAS HAND FLYING A VISUAL APCH TO RWY 30R AT MSP AND NOTICED A 30 DEG MAP SHIFT ON OUR SCREENS. KNOWING THE ARPT EXTREMELY WELL (MY NEIGHBORHOOD), I CONTINUED THE VISUAL USING PAPI AND RAW DATA. ON SHORT FINAL OVER THE RIVER TO RWY 30R, WE HAD THE 'TERRAIN, PULL-UP-PULL-UP' COMMANDS. AGAIN, I CONTINUED MY VISUAL SLIGHTLY ABOVE THE NORMAL GS WITH COMPLETELY VISUAL CONDITIONS. I WAS FULLY AWARE OF THE BOGUS TERRAIN COMMANDS DUE TO THE SHIFT OF SCREENS SHOWING US WELL TO THE S OF COURSE. I MADE A NORMAL LNDG ON RWY 30R AND WE CALLED AND MADE A LOGBOOK WRITE-UP. SUPPLEMENTAL INFO FROM ACN 595185: ON APCH TO MSP, NIGHT VFR, FMC POS WAS OFF ABOUT 10 MI AND SHOWED ABOUT 30 DEGS OFF HDG REF. BDHI. CAP'S NAV PANEL WAS ON AUTO. I SHIFTED TO MANUAL AND BACK TO AUTO. THE HDG ALIGNED FOR A FEW SECONDS, AND THEN SHIFTED OFF AGAIN.
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.