37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1067454 |
Time | |
Date | 201302 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | D01.TRACON |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Beechjet 400 |
Operating Under FAR Part | Part 135 |
Flight Phase | Descent |
Route In Use | STAR SKARF2 |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Other / Unknown |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 115 Flight Crew Total 3000 Flight Crew Type 1400 |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
ATC (ZLA) originally assigned us direct tomsn - tomsn six arrival. Denver center asked if we were RNAV capable (yes) then assigned us the skarf two. We loaded the skarf two into the FMS and checked all the waypoints and associated altitudes and airspeeds. The first waypoint that showed in the FMS was archy. This agreed with the page we were referring to in the approach plate. We were direct tomsn when denver approach cleared us to descend via the skarf 2. The first point we were aware of for this arrival was archy with a hard altitude of 15;000 ft. Outside of tomsn the pilot flying began a descent for 15;000. Passing through 17;500 and passing tomsn ATC advised us we were to be between FL220 and FL200 passing tomsn. They then gave us 'maintain 17;000'. There were no conflicts with other aircraft.we referred back to the approach plate and found that we missed page 1 of the skarf two. Page 1 makes it clear to continue to the next page for the rest of the arrival; however; page 2 has no notation that there is a page 1. We also went back and reloaded the arrival in our FMS twice to verify that the first waypoint that shows up is archy. These two items led to us missing the beginning of the arrival. This RNAV arrival along with several others was new in november. If there are no corrections (a notation on page 2 that there is a prior page) I anticipate further problems.
Original NASA ASRS Text
Title: When cleared to 'descend via' the SKARF STAR to DEN the flight crew of a BE400 failed to note the arrival consisted of two pages; the first the en route transitions and the second the common portion. When ATC advised they had missed a crossing restriction that was displayed on the transition page they realized their error; which they attributed to the fact that; although the first page directed them to the second; the second (which they located first) failed to similarly direct them to the first.
Narrative: ATC (ZLA) originally assigned us direct TOMSN - TOMSN Six arrival. Denver Center asked if we were RNAV capable (yes) then assigned us the SKARF Two. We loaded the SKARF Two into the FMS and checked all the waypoints and associated altitudes and airspeeds. The first waypoint that showed in the FMS was ARCHY. This agreed with the page we were referring to in the approach plate. We were direct TOMSN when Denver Approach cleared us to descend via the SKARF 2. The first point we were aware of for this arrival was ARCHY with a hard altitude of 15;000 FT. Outside of TOMSN the pilot flying began a descent for 15;000. Passing through 17;500 and passing TOMSN ATC advised us we were to be between FL220 and FL200 passing TOMSN. They then gave us 'maintain 17;000'. There were no conflicts with other aircraft.We referred back to the approach plate and found that we missed page 1 of the SKARF two. Page 1 makes it clear to continue to the next page for the rest of the arrival; however; page 2 has no notation that there is a page 1. We also went back and reloaded the arrival in our FMS twice to verify that the first waypoint that shows up is ARCHY. These two items led to us missing the beginning of the arrival. This RNAV arrival along with several others was new in November. If there are no corrections (a notation on page 2 that there is a prior page) I anticipate further problems.
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.