37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 339605 |
Time | |
Date | 199606 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : crg |
State Reference | FL |
Altitude | msl bound lower : 29000 msl bound upper : 29000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zjx |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | cruise other |
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 : 13500 flight time type : 2500 |
ASRS Report | 339605 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation other |
Narrative:
Departed mco for lga on normal preferred flight plan. Extensive deviating after takeoff due to numerous thunderstorms in central florida region. After 20 plus mins of flight I turned and intercepted our flight plan route close to jax (crg). Both flight management computers showed us on course, however, ZJX inquired about our 'present course' being flown. On double checking with raw data navigation we were actually 30 mi south of our FMC indicated position. The captain and I attempted to update FMC position manually but computer wouldn't accept inputs. Fmcs also would not 'automatic update position' from the IRS's. The initial latitude and longitude position input was checked prior to the flight and was correct, no doubt about that fact by either pilot. ATC pointed us direct our next route fix and the flight continued uneventfully using 'low technology,' accurate input. There was no conflict or problem stated by ATC. Fmcs was logged inoperative for maintenance at lga. Flight crew changed aircraft. Since the fmcs wouldn't update manually, automatically, or allow for position shift I feel certain that part of the system had failed.
Original NASA ASRS Text
Title: A B737 FO RPTS OF AN FMC MALFUNCTION THAT LED TO A 30 NM COURSE DEV BEFORE IT WAS DISCOVERED. THE FMC FAILED TO ACCEPT ANY INPUT TO REPAIR THE SIT FROM THE FLC. THE FLC HAD BEEN DEVIATING FOR WX AND THOUGHT THAT THEY HAD REJOINED THE FLT PLAN RTE WHEN ATC QUERIED THEIR COURSE.
Narrative: DEPARTED MCO FOR LGA ON NORMAL PREFERRED FLT PLAN. EXTENSIVE DEVIATING AFTER TKOF DUE TO NUMEROUS TSTMS IN CENTRAL FLORIDA REGION. AFTER 20 PLUS MINS OF FLT I TURNED AND INTERCEPTED OUR FLT PLAN RTE CLOSE TO JAX (CRG). BOTH FLT MGMNT COMPUTERS SHOWED US ON COURSE, HOWEVER, ZJX INQUIRED ABOUT OUR 'PRESENT COURSE' BEING FLOWN. ON DOUBLE CHKING WITH RAW DATA NAV WE WERE ACTUALLY 30 MI S OF OUR FMC INDICATED POS. THE CAPT AND I ATTEMPTED TO UPDATE FMC POS MANUALLY BUT COMPUTER WOULDN'T ACCEPT INPUTS. FMCS ALSO WOULD NOT 'AUTO UPDATE POS' FROM THE IRS'S. THE INITIAL LATITUDE AND LONGITUDE POS INPUT WAS CHKED PRIOR TO THE FLT AND WAS CORRECT, NO DOUBT ABOUT THAT FACT BY EITHER PLT. ATC POINTED US DIRECT OUR NEXT RTE FIX AND THE FLT CONTINUED UNEVENTFULLY USING 'LOW TECHNOLOGY,' ACCURATE INPUT. THERE WAS NO CONFLICT OR PROB STATED BY ATC. FMCS WAS LOGGED INOP FOR MAINT AT LGA. FLC CHANGED ACFT. SINCE THE FMCS WOULDN'T UPDATE MANUALLY, AUTOMATICALLY, OR ALLOW FOR POS SHIFT I FEEL CERTAIN THAT PART OF THE SYS HAD FAILED.
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.