 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of a B737 were not on the STAR arrival routing due to an aircraft navigational position computing error resulting in ATC intervention to bring reporter back to assigned routing track.
| Attributes | |
| ACN | 368760 |
| Time | |
| Date | 199705 |
| Day | Fri |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : pxn |
| State Reference | CA |
| Altitude | msl bound lower : 26000 msl bound upper : 26000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zoa |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other |
| Flight Phase | cruise other descent other |
| Route In Use | arrival other arrival star : star |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | controller military : 13 controller non radar : 3 controller radar : 18 flight time last 90 days : 190 flight time total : 5800 flight time type : 3300 |
| ASRS Report | 368760 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial |
| Events | |
| Anomaly | aircraft equipment problem : less severe non adherence : clearance other anomaly other other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | flight crew : returned to intended course or assigned course other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Aircraft |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Given clearance to descend on the arrival into oak. Started descent and noticed TCASII traffic within 8 NM and 200 ft vertical. Center then asked if we were on the arrival. Our navigation equipment confirmed we were (or within 2 NM maximum error passing over VOR due to slant range problems). We received a TCASII TA and turned away from traffic. I later talked with center and they said we were about 7 mi left of course. Our equipment never indicated that much error. En route to oak everything appeared okay.
Original NASA ASRS Text
Title: FLC OF A B737 WERE NOT ON THE STAR ARR ROUTING DUE TO AN ACFT NAVIGATIONAL POS COMPUTING ERROR RESULTING IN ATC INTERVENTION TO BRING RPTR BACK TO ASSIGNED ROUTING TRACK.
Narrative: GIVEN CLRNC TO DSND ON THE ARR INTO OAK. STARTED DSCNT AND NOTICED TCASII TFC WITHIN 8 NM AND 200 FT VERT. CTR THEN ASKED IF WE WERE ON THE ARR. OUR NAV EQUIP CONFIRMED WE WERE (OR WITHIN 2 NM MAX ERROR PASSING OVER VOR DUE TO SLANT RANGE PROBS). WE RECEIVED A TCASII TA AND TURNED AWAY FROM TFC. I LATER TALKED WITH CTR AND THEY SAID WE WERE ABOUT 7 MI L OF COURSE. OUR EQUIP NEVER INDICATED THAT MUCH ERROR. ENRTE TO OAK EVERYTHING APPEARED OKAY.
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.