37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1066973 |
Time | |
Date | 201302 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Challenger 605 |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | STAR RIIVR2 |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Altitude Undershoot Deviation - Procedural Clearance |
Narrative:
While on the riivr RNAV STAR into lax; we were cleared direct to gramm intersection. The PF briefed the ILS for runway 25L and 24R; not knowing which was to be assigned. We continued on the arrival approaching rustt intersection at which point we were told to expect the ILS for 24R. Having already loaded the ILS for 25L (hopeful thinking); I proceeded to load the change in the FMS. Referring to the riivr arrival; I didn't see a transition for the north complex and questioned socal if they still wanted us on the riivr arrival; to which they responded 'affirmative'. At this time; we were approaching 14;000 feet MSL with VNAV selected. Socal instructed us to expedite down to 10;000 feet and cleared us direct to skoll intersection. The PF selected 10;000 feet in the window and we both acknowledged the selection. As the PNF; I returned my attention to trying to load the FMS with the ILS for 24R; but couldn't find the transition from the riivr arrival. With the ILS 24R in the FMS; skoll intersection; did not appear. During this confusion; the controller came on with a very harsh scolding of our failure to expeditiously descend to 10;000 feet. Because I did not put a direct to skoll command in the FMS yet; with VNAV still active; the aircraft was maintaining 14;000 feet until passing habso. The controller then came back with the statement that it looked as though we were lining up for 25L and instructed us to turn right to a heading [I've forgotten] to intercept the ILS 24R localizer. The PF immediately deselected VNAV; descended to 10;000 feet and made the turn to intercept the localizer for 24R. All this occurred within approximately a 30 second time frame. The remainder of the flight continued as planned.after landing; we debriefed the event quite extensively and in doing so; realized that there is a riivr transition for the ILS 24R in the FMS on the second page of transitions. Had I not focused on the arrival and spent more time on the approach chart; I should have caught the oversight. It was also discussed that once an altitude clearance is assigned while on an arrival; deselecting VNAV should be a consideration. We both concluded that the combination of the time constraint and the 'colorful briefing' by the controller only added to what had already become a high stress environment.
Original NASA ASRS Text
Title: The flight crew of a corporate CL-605 cleared via the RIIVR STAR to LAX was caught short when Approach Control advised them to expect Runway 24R vice 25L as depicted on the arrival. Difficulty reprogramming the FMS for the new ILS resulted in autoflight remaining in VNAV PATH and the aircraft leveled at 14;000 feet instead of expediting to 10;000 feet as requested by Approach.
Narrative: While on the RIIVR RNAV STAR into LAX; we were cleared direct to GRAMM intersection. The PF briefed the ILS for Runway 25L and 24R; not knowing which was to be assigned. We continued on the arrival approaching RUSTT intersection at which point we were told to expect the ILS for 24R. Having already loaded the ILS for 25L (hopeful thinking); I proceeded to load the change in the FMS. Referring to the RIIVR Arrival; I didn't see a transition for the North complex and questioned SoCal if they still wanted us on the RIIVR Arrival; to which they responded 'affirmative'. At this time; we were approaching 14;000 feet MSL with VNAV selected. SoCal instructed us to expedite down to 10;000 feet and cleared us direct to SKOLL intersection. The PF selected 10;000 feet in the window and we both acknowledged the selection. As the PNF; I returned my attention to trying to load the FMS with the ILS for 24R; but couldn't find the transition from the RIIVR arrival. With the ILS 24R in the FMS; SKOLL intersection; did not appear. During this confusion; the controller came on with a very harsh scolding of our failure to expeditiously descend to 10;000 feet. Because I did not put a direct to SKOLL command in the FMS yet; with VNAV still active; the aircraft was maintaining 14;000 feet until passing HABSO. The Controller then came back with the statement that it looked as though we were lining up for 25L and instructed us to turn right to a heading [I've forgotten] to intercept the ILS 24R LOC. The PF immediately deselected VNAV; descended to 10;000 feet and made the turn to intercept the LOC for 24R. All this occurred within approximately a 30 second time frame. The remainder of the flight continued as planned.After landing; we debriefed the event quite extensively and in doing so; realized that there is a RIIVR transition for the ILS 24R in the FMS on the second page of transitions. Had I not focused on the Arrival and spent more time on the approach chart; I should have caught the oversight. It was also discussed that once an altitude clearance is assigned while on an arrival; deselecting VNAV should be a consideration. We both concluded that the combination of the time constraint and the 'colorful briefing' by the Controller only added to what had already become a high stress environment.
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.