Date: 201303
Local time of day: 1801-2400
Location: DEN.Airport, CO
Light: Daylight
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class E D01
ATC / advisory: TRACON D01
Aircraft component: FMS/FMC
Component problem: Design
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Human factors: Human-Machine Interface; Situational Awareness
Second reporter function: Pilot Flying; Captain
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Aircraft; Chart Or Publication; Human Factors
Primary problem: Human Factors

Narrative: Departed DEN 17R on BAYLR1 RNAV departure cleared to 10;000 FT between YORVT and HURDL waypoints at 10;000 FT and accelerating. ATC instructed us to 'Climb and maintain FL230; comply with RNAV departure'. Pilot flying was hand flying; pilot not flying put 23000 in FCP altitude window. Then all the altitude constraints programmed in the FMS disappeared from the FMS flight plan and the NAV display. The FMS directed an immediate climb. Absent the FMS guidance; pilot not flying tried to reference the Commercial paper charts; but the airplane has an Electronic Flight Bag (EFB) bracket instead of a paper holder clip (EFB's are deactivated and placed in the closet) so the paper charts had fallen out of sight. By the time the pilot not flying could reference paper Commercial Charts; the aircraft had climbed to 11;000 FT. The constraint at the next point HURDL is at or below 10;000 FT. ATC instructed to 'Stop climb at 12;000 FT' and then gave further altitude and heading assignments. Prior to handing us off to next Controller; ATC confirmed that we knew 'comply with RNAV departure' meant to comply with altitude restrictions. Prior to setting a new altitude in the FCP during RNAV climbout departure; I need to confirm that no AT OR BELOW altitudes will be violated. This is because the A300 FMS does not honor AT OR BELOW altitudes when a new altitude is set. The constraints drop out of the FMS and the NAV display. The paper charts don't work very well with the EFB bracket installed and tend to fall to the floor on takeoff. This was a mistake that happened very quickly and the lack of a handy chart was a player.


Second narrative: Prior to setting a new altitude in the FCP during climb; confirm that no AT OR BELOW altitudes will be violated. The A300 FMS does not honor AT OR BELOW altitudes in a climb. Also; improvise a way to keep charts within reach when there is no installed chart clip. Rubber bands; clips; or some other means needs to be used to secure the charts.


Synopsis: A300 flight crew describes inadvertent deletion of altitude constraints during the BAYLR1 RNAV departure from DEN. The available paper charts had fallen to the floor and could not be quickly accessed resulting in exceeding a crossing restriction.