37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1177070 |
Time | |
Date | 201405 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZLA.ARTCC |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 11000 Flight Crew Type 150 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Upon departing lgb and after a few handoffs and climb instructions; one controller at la center gave us a re-routing. This new route included adding two new fixes to our flight plan: fixit & ikaye. So the new route was direct to fixit - ikaye - rzs. As the pilot flying I was focused on aircraft control while the pilot not flying was making the appropriate changes on the FMS. I acknowledged the first direct (to fixit) and proceeded to engage LNAV to fixit. We were not too far from this fix by the time I proceeded direct to this fix. Moments after crossing fixit the pilot flying realized that we were proceeding to rzs instead of ikaye and notified ATC of this deviation. Workload in the cockpit prior to receiving the re-route was above normal. The new route was properly received; acknowledged; and read back to ATC. The pilot not flying and I were not familiar with this fixes; and the pilot not flying had to confirm the spelling of both way points; and then properly identify them on our navigation charts. We feel that we were too close to the above mentioned fixes in order to properly (and correctly) load the fixes on the FMS and perform a cross check with both pilots about the new FMS changes. The deviation was discovered by the pilot flying just moments after crossing the first new fix (fixit) and I proceeded to make an immediate right turn towards the fix while the pilot not flying informed ATC about this error.
Original NASA ASRS Text
Title: Pilot complains about re-route with fixes they are not familiar with and having to enter them to the FMS; while flying close to the first intersection.
Narrative: Upon departing LGB and after a few handoffs and climb instructions; one Controller at LA Center gave us a re-routing. This new route included adding two new fixes to our flight plan: FIXIT & IKAYE. So the new route was direct to FIXIT - IKAYE - RZS. As the pilot flying I was focused on aircraft control while the pilot not flying was making the appropriate changes on the FMS. I acknowledged the first direct (to FIXIT) and proceeded to engage LNAV to FIXIT. We were not too far from this fix by the time I proceeded direct to this fix. Moments after crossing FIXIT the pilot flying realized that we were proceeding to RZS instead of IKAYE and notified ATC of this deviation. Workload in the cockpit prior to receiving the re-route was above normal. The new route was properly received; acknowledged; and read back to ATC. The pilot not flying and I were not familiar with this fixes; and the pilot not flying had to confirm the spelling of both way points; and then properly identify them on our navigation charts. We feel that we were too close to the above mentioned fixes in order to properly (and correctly) load the fixes on the FMS and perform a cross check with both pilots about the new FMS changes. The deviation was discovered by the pilot flying just moments after crossing the first new fix (FIXIT) and I proceeded to make an immediate right turn towards the fix while the pilot not flying informed ATC about this error.
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.