 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot reports of unfamiliarity with a couple of fixes and having problems loading them into the FMS.
| Attributes | |
| ACN | 1176712 |
| Time | |
| Date | 201405 |
| Local Time Of Day | 1801-2400 |
| 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 | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 40 Flight Crew Total 7600 Flight Crew Type 285 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
I am doing my best to try to recollect the altitude and other details about the flight. We departed long beach airport from runway 30. We were given radar vectors to exert. We were given several frequency changes; altitude assignments and headings. At some point during the climb we were advised by la center about a re-routing (fixit-ikaye-rzs). Since I was not familiar with these fixes; I had to ask for the spelling of these two way points: fixit and ikaye. I was able to identify fixit and load it on the FMS; and then offer the pilot flying (PF) a direct to that fix from the FMS. When I modified the FMS; I programmed fixit as the active way point followed by rzs; while I located the other new way point (ikaye) I wanted to make sure I was able to locate ikaye before adding it to the FMS. I should point out that our original clearance (exert - V25 - rzs) would have kept us outside the R-2519 airspace. So; in looking back; I am not sure what the need for this re-route was; considering that I believe we were very close to these fixes to begin with. I entered the first fix into the FMS (fixit) and offered LNAV to the PF. By the time I was able to find and identify the next fix on the chart (ikaye); I had just realized that we had crossed fixit; and proceeded to notify the PF to make a right turn towards ikaye; and I also notified ATC immediately of this error; as we were turning to the north towards ikaye.
Original NASA ASRS Text
Title: Pilot reports of unfamiliarity with a couple of fixes and having problems loading them into the FMS.
Narrative: I am doing my best to try to recollect the altitude and other details about the flight. We departed Long Beach Airport from Runway 30. We were given radar vectors to EXERT. We were given several frequency changes; altitude assignments and headings. At some point during the climb we were advised by LA Center about a re-routing (FIXIT-IKAYE-RZS). Since I was not familiar with these fixes; I had to ask for the spelling of these two way points: FIXIT and IKAYE. I was able to identify FIXIT and load it on the FMS; and then offer the Pilot Flying (PF) a direct to that fix from the FMS. When I modified the FMS; I programmed FIXIT as the active way point followed by RZS; while I located the other new way point (IKAYE) I wanted to make sure I was able to locate IKAYE before adding it to the FMS. I should point out that our original clearance (EXERT - V25 - RZS) would have kept us outside the R-2519 airspace. So; in looking back; I am not sure what the need for this re-route was; considering that I believe we were very close to these fixes to begin with. I entered the first fix into the FMS (FIXIT) and offered LNAV to the PF. By the time I was able to find and identify the next fix on the chart (IKAYE); I had just realized that we had crossed FIXIT; and proceeded to notify the PF to make a right turn towards IKAYE; and I also notified ATC immediately of this error; as we were turning to the north towards IKAYE.
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.