 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A320 first officer reported a track deviation and cftt occurred on arrival into tus following a late clearance change.
| Attributes | |
| ACN | 1616221 |
| Time | |
| Date | 201902 |
| Place | |
| Locale Reference | TUS.Airport |
| State Reference | AZ |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 171 Flight Crew Type 575 |
| Events | |
| Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
With strong and gusty winds gusting to 29 knots; we planned on runway 21 and set up for the RNAV 21 at tus. We were not assigned a via segment and therefore; did not include that in the FMGC and anticipated radar vectors to final approach course. Upon checking in with the approach controller; I realized it was very congested airspace and the controller advised us to expect direct raina and to get set up for it. The captain attempted to insert the vias with the associated RNAV 21. The controller gave us an initial heading and then maybe a minute later came back and asked us if we were set up for raina. The captain manually input it into the direct to since he could not get it to load in the via. I acknowledged the fix and proceeded direct to it. Immediately; we realized there was a problem and I reverted back to last assigned heading [while] the captain re-inserted the correct spelling of raina in the direct to function. However; because of this delay; we ended up navigating a right 270 that took us towards terrain to reach the fix. We were [queried] by the controller and then assigned 1000 foot climb in altitude to 11;000 feet. The rest of the approach was uneventful. We debriefed the event as a crew.
Original NASA ASRS Text
Title: A320 First Officer reported a track deviation and CFTT occurred on arrival into TUS following a late clearance change.
Narrative: With strong and gusty winds gusting to 29 knots; we planned on Runway 21 and set up for the RNAV 21 at TUS. We were not assigned a VIA segment and therefore; did not include that in the FMGC and anticipated radar vectors to final approach course. Upon checking in with the Approach Controller; I realized it was very congested airspace and the controller advised us to expect direct RAINA and to get set up for it. The Captain attempted to insert the vias with the associated RNAV 21. The Controller gave us an initial heading and then maybe a minute later came back and asked us if we were set up for RAINA. The Captain manually input it into the direct to since he could not get it to load in the Via. I acknowledged the fix and proceeded direct to it. Immediately; we realized there was a problem and I reverted back to last assigned heading [while] the Captain re-inserted the correct spelling of RAINA in the direct to function. However; because of this delay; we ended up navigating a right 270 that took us towards terrain to reach the fix. We were [queried] by the Controller and then assigned 1000 foot climb in altitude to 11;000 feet. The rest of the approach was uneventful. We debriefed the event as a crew.
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.