A B737-500 flight crew had a track deviation when their attempt to program a 'direct to a fix with intervening abeam points' went awry. The lack of a moving map Navigation Display was cited as a contributing factor.

2011-06 · NASA ASRS report 952769

Date: 2011-06 · Aircraft: B737-500 · Phase: descent

Anomalies: aircraft-equipment-problem-less-severe|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance

Synopsis

A B737-500 flight crew had a track deviation when their attempt to program a 'direct to a fix with intervening abeam points' went awry. The lack of a moving map Navigation Display was cited as a contributing factor.

Narrative

ATC vectored us to 030 degrees for traffic; then re-cleared us direct BOWEN. I selected 'BOWEN; Page1; ABEAM POINTS; Execute (I saw the abeam points repopulated) then LNAV; and VNAV switches down.' The aircraft turned back onto course 30 degrees back to heading prior to 30 degree vector. This was the wrong direction. What I believe happened is the FMC did not receive the 'execute' command either because I did not hit it or it did not accept the BOWEN abeam points. Regardless; the aircraft turned the wrong direction when I selected LNAV. ATC queried our turn. We again line selected BOWEN without the abeam points and turned back direct BOWEN. I was not spatially aware that BOWEN was another 30 degrees to the left of course; so when the aircraft turned right; it did not raise my suspicions because I thought we were turning back on course toward our previous heading. Since I believed I hit all the right buttons and saw the abeams populate to BOWEN; when the aircraft turned; I felt I was turning in the correct direction. I need to confirm the heading to the next point I line select to the top of Page 1 and before hitting abeam point note the heading to ensure the aircraft turns to the correct heading.

Second reporter narrative

A few minutes later; Boston called out traffic climbing on the right side. The remainder of the flight was uneventful. My assumption was that we were going direct BOWEN upon the FMC execution that turned right from the 030 vector. I did not know that BOWEN was to the left of the vector. It appears that that as the new course was not actually selected in the FMC; the aircraft simply turned toward the previous LNAV FMC point from before the vector into the traffic it appears they wanted to vector us from. After today; I recommend no longer using abeam points; as the primary point often ends up on Legs Page 2 (or more); as it did today. For those that insist on using abeam points; the course must be confirmed to the point before executing; followed by confirming the '01' courses are similar. The lack of a map display was a primary factor in our lack of situational awareness of the fix position.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.