37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1120194 |
Time | |
Date | 201310 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZNY.ARTCC |
State Reference | NY |
Aircraft 1 | |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
ATC re-route by lga clearance delivery. Original flight plan route was; lga dct white J209 sby dct diw ... Revised clearance; lga 4 departure runway 31; right turn heading 359; radar vectors jfk; wavie; emjay; J174 swl cebee wetro dix ... Normal departure and climb until ATC cleared us direct wavie. I selected wavie to 1L ...yup looks good; like that? LNAV. As we are rolling through a heading 270; ATC informs us we are 'off course' and re-clears us dct wavie. Wavie is in 1L and LNAV is engaged pointing us further to the right. ATC then gives us a 'heading 180 dct wavie when able.' it dawns on me to ask for the phonetic spelling of wavie . ATC replies 'whiskey alpha victor echo yankee...... Wavey.' I corrected the spelling of wavie in 1L; and it provided a heading of 150; LNAV engaged again and all is well. I explain to ATC the wavie vs. Wavey input error (on my part during the re-route on the ground) and received a bemused chuckle from ATC. They didn't seem at all surprised by this; more like we were just one more flight crew who fell into that trap. 1) mileage on prog page was significantly more; so we checked all the points again; 3 times!!! Paper to glass; glass to paper et al. We thought the mileage discrepancy was due to route discontinuities on both the departure; and arrival ends. 2) we did not have a new flight plan so could not check heading and distance to next waypoint to see if it makes sense only the flight plan review. I am reading wavie; and my first officer is hearing (and seeing wavey on the flight plan review) what's the problem? 3) short of checking the spelling for each point; you would have to check the heading on the FMC to the next point to see if it makes sense; and we do not do that. One pilot reads the points off the nd for continuity; and the other pilot confirms them against the flight plan paper copy. You would need to do international procedures (like on the over water portion of the nat) to catch this.
Original NASA ASRS Text
Title: B737 Captain reports being issued a reroute from LGA via LGA4 heading 359 for vectors to JFW; WAVEY ... except WAVEY is spelled WAVIE and the error is not detected and a track deviation results.
Narrative: ATC re-route by LGA Clearance Delivery. Original flight plan route was; LGA DCT WHITE J209 SBY DCT DIW ... Revised clearance; LGA 4 DEP RWY 31; RIGHT TURN HDG 359; RADAR VECTORS JFK; WAVIE; EMJAY; J174 SWL CEBEE WETRO DIX ... Normal departure and climb until ATC cleared us direct WAVIE. I selected WAVIE to 1L ...yup looks good; like that? LNAV. As we are rolling through a HDG 270; ATC informs us we are 'off course' and re-clears us DCT WAVIE. WAVIE is in 1L and LNAV is engaged pointing us further to the right. ATC then gives us a 'heading 180 DCT WAVIE when able.' It dawns on me to ask for the phonetic spelling of WAVIE . ATC replies 'Whiskey Alpha Victor Echo Yankee...... WAVEY.' I corrected the spelling of WAVIE in 1L; and it provided a heading of 150; LNAV engaged again and all is well. I explain to ATC the WAVIE vs. WAVEY input error (on my part during the re-route on the ground) and received a bemused chuckle from ATC. They didn't seem at all surprised by this; more like we were just one more flight crew who fell into that trap. 1) Mileage on PROG page was significantly more; so we checked all the points again; 3 times!!! Paper to glass; glass to paper et al. We thought the mileage discrepancy was due to route discontinuities on both the departure; and arrival ends. 2) We did not have a new flight plan so could not check heading and distance to next waypoint to see if it makes sense only the flight plan review. I am reading WAVIE; and my First Officer is hearing (and seeing WAVEY on the flight plan review) what's the problem? 3) Short of checking the spelling for each point; you would have to check the heading on the FMC to the next point to see if it makes sense; and we do not do that. One pilot reads the points off the ND for continuity; and the other pilot confirms them against the flight plan paper copy. You would need to do international procedures (like on the over water portion of the NAT) to catch this.
Data retrieved from NASA's ASRS site as of July 2013 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.