37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1706814 |
Time | |
Date | 201912 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZLA.ARTCC |
State Reference | CA |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Component | |
Aircraft Component | Navigation Database |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Shortly after takeoff from dal; fort worth center cleared us direct to pgs on the tyssn 5 arrival. We were originally filed on the tyssn 5.igm. I manually entered pgs at the top of legs page 1. I then had to delete the old points from the igm transition. When completed; I did not notice that the cejay and kaddy points did not load. Later on; I failed to do the arrival briefing; which would have captured this error. When I looked at the legs page; I saw what I expected to see; not what was actually there. During the arrival; la center told us we were north of course (because we were going pgs direct to tyssn instead of pgs.cejay.kaddy.tyssn). La center cleared us direct to kaddy; and we had no problem making the 12;000 feet and 250 knots kaddy restriction. Incidentally; before we figured out the missing waypoints error; we thought our north-of-course error was due to an intermittent GPS-left error message that began near the white sands missile range. We assumed GPS jamming was in effect and had caused the navigation error. But we later discovered the error on the legs page. Expectation bias led me to being complacent about a required descent briefing. Had I done the briefing completely; the error would have been easily captured.
Original NASA ASRS Text
Title: B-737 Captain reported a course deviation caused by an error in loading the STAR into the FMS.
Narrative: Shortly after takeoff from DAL; Fort Worth Center cleared us direct to PGS on the TYSSN 5 Arrival. We were originally filed on the TYSSN 5.IGM. I manually entered PGS at the top of LEGS Page 1. I then had to delete the old points from the IGM transition. When completed; I did not notice that the CEJAY and KADDY points did not load. Later on; I failed to do the arrival briefing; which would have captured this error. When I looked at the LEGS Page; I saw what I expected to see; not what was actually there. During the arrival; LA Center told us we were north of course (because we were going PGS direct to TYSSN instead of PGS.CEJAY.KADDY.TYSSN). LA Center cleared us direct to KADDY; and we had no problem making the 12;000 feet and 250 knots KADDY restriction. Incidentally; before we figured out the missing waypoints error; we thought our north-of-course error was due to an intermittent GPS-L error message that began near the White Sands Missile Range. We assumed GPS jamming was in effect and had caused the navigation error. But we later discovered the error on the LEGS Page. Expectation bias led me to being complacent about a required descent briefing. Had I done the briefing completely; the error would have been easily captured.
Data retrieved from NASA's ASRS site 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.