Date: 201310
Local time of day: 1801-2400
Location: ZLA.ARTCC, CA
Flight conditions: VMC
Light: Night
Aircraft: Challenger 300
Operator: Corporate
Operating under: Part 91
Flight phase: Descent
Airspace: Class E ZLA
ATC / advisory: Center ZLA
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Fractional
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Just outside MYCAL Intersection on the ADDEL ONE RNAV Arrival into HND. Center cleared us to cross FUZZY Intersection at 250 KTS and 16;000 FT. Both crew verified the correct altitude was placed in the alerter and VNAV was armed. Both crew verified the speed and altitude was in the FMS our eyes thought. JARIK Intersection 7.2 miles ahead; is built on the arrival with at 250 KTS; at 16;000. We crossed FUZZY around 17;500 FT? Upon checking on with Las Vegas Approach we realized prior to communicating our altitude that we had missed the cross. Approach didn't seem concerned. At no time was the aircraft in danger. Las Vegas has complex RNAV arrivals. They consistently change the crossing altitudes from what is posted. In this case if they had just told us to descend via the arrival; there would have been no problem. Is changing a crossing restriction for 7.2 miles really needed? Las Vegas should decide to either post JARIK or FUZZY Intersection at 16;000. Crew needs to be more diligent when cross checking FMS.


Second narrative: We were flying the ADDEL 1 Arrival; as cleared by Los Angeles Center. The crew had briefed the arrival; including the checking of the fixes; crossing altitudes and speeds on the chart; against the pre-loaded fixes/altitudes/speeds in the FMS. ATC issued a clearance to cross 'FUZZY' Intersection at 16;000 and 250 KTS. After the readback; the crew confirmed the ATC crossing clearance with each other per SOP's; and then armed the V-NAV on the auto pilot. I had noticed the 16;000/250 posted next to 'FUZZY' on my MFD Map. I then cross-checked the FMS for the entered crossing restriction; and thought I saw 'FUZZY at 16;000. During our descent and about 2 miles from 'FUZZY'; LA Center told us to contact Las Vegas Approach. At that time; we noticed we still had the published and 'pre-loaded' 250/16;000 over 'JARIK' Intersection in our FMS box. (JARIK Intersection is 7.2 miles after FUZZY Intersection) we then quickly expedited our descent to 16;000 FT. We checked in with Las Vegas Approach and were cleared to 14;000 FT. We crossed FUZZY Intersection at approximately 17;000 FT during our descent to 16;000. There was no conflict with other aircraft. There was no mention from Las Vegas Approach about our crossing altitude clearance. The flight continued via the ADDEL 1 arrival uneventfully to HND.Never rely on a posted crossing restriction on your MFD. It can be confusing when fixes are that close together (7 miles). Always check; and recheck; the assigned crossing clearance that is loaded in the FMS. Never assume ATC is descending you with the same altitudes/speeds that are published and pre-loaded in the FMS on a arrival. Summary- be more diligent when cross checking the FMS.


Synopsis: CL300 flight crew reports not making their crossing restriction on the ADDEL 1 into HND due to an improper FMC entry.