A321 captain reported being unable to meet crossing restrictions while on the trailer 9 SID.

Attributes
ACN	1648144
Time
Date	201905
Local Time Of Day	1801-2400
Place
Locale Reference	LAS.Airport
State Reference	NV
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	A321
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID TRALR9
Flight Plan	IFR
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 150 Flight Crew Total 21000 Flight Crew Type 11000
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Undershoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Narrative:

The controller told us to file a report because 'the FAA was looking into 321s not making the climb restriction.' controller also mentioned something about 'using runway 01R with this SID and having other options.' and also said they are looking into us knowingly accepting a clearance we cannot make. The fix in question is rioos on the trailer 9 SID at or above 13;000 MSL without a speed requirement. Once airborne if the controller needed the altitude and was unable to offer a delay vector then I could slow down (i.e. Climb faster) or add power to make the restriction. As far as takeoff options were concerned; the wind was 330/20g27kt; so a takeoff on 26R at our weight would not be a safe option. We were heavy and the FMC did predict we would be lower than required at rioos; at 320 KTS. The cost index was set to 55 and I had programmed the current temperature; which would give the FMC a better prediction; but it is still just a prediction to use for information on the ground. A NOTAM for las stating that ATC will not offer vectors or reduced speed to make the climb restrictions; and making rioos a mandatory altitude with a speed requirement.

Original NASA ASRS Text

Title: A321 Captain reported being unable to meet crossing restrictions while on the Trailer 9 SID.

Narrative: The Controller told us to file a report because 'the FAA was looking into 321s not making the climb restriction.' Controller also mentioned something about 'using Runway 01R with this SID and having other options.' And also said they are looking into us knowingly accepting a clearance we cannot make. The fix in question is RIOOS on the Trailer 9 SID at or above 13;000 MSL without a speed requirement. Once airborne if the Controller needed the altitude and was unable to offer a delay vector then I could slow down (i.e. climb faster) or add power to make the restriction. As far as takeoff options were concerned; the wind was 330/20G27KT; so a takeoff on 26R at our weight would not be a safe option. We were heavy and the FMC did predict we would be lower than required at RIOOS; at 320 KTS. The cost index was set to 55 and I had programmed the current temperature; which would give the FMC a better prediction; but it is still just a prediction to use for information on the ground. A NOTAM for LAS stating that ATC will not offer vectors or reduced speed to make the climb restrictions; and making RIOOS a mandatory altitude with a speed requirement.

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.