Narrative:

Departing lax; dotss 2 departure assigned 5000 ft. We were give several turns and then direct pevee climbing to 9000 ft then 12000 ft then issued 'climb via SID' then FL230. While in the turn to pevee the preceding aircraft reported sighting a drone at 13000 ft. We wanted to clarify the climb via instruction and get a vector left to avoid the area of the drone sighting. Once the captain was able to finally ask for clarification the controller issued a climb to FL230 and stated 'you're not going to make that climb restriction here's the number to call for a pilot deviation.' we were still at 12000 ft and approximately 17 NM from the 15000 ft or above restriction at dotss when he made that pronouncement. We ended up crossing dotss at approximately 17000 ft.after speaking with a supervisor at the socal ATC faculty; it seems the controller was a bit task saturated with the drone in the area and coordinating with other aircraft. He also stated there was no violation.

Related reports:

Google
 

Original NASA ASRS Text

Title: A321 flight crew reported being distracted by reports of a drone on departure from LAX.

Narrative: Departing LAX; DOTSS 2 departure assigned 5000 ft. We were give several turns and then direct PEVEE climbing to 9000 ft then 12000 ft then issued 'climb via SID' then FL230. While in the turn to PEVEE the preceding aircraft reported sighting a drone at 13000 ft. We wanted to clarify the climb via instruction and get a vector left to avoid the area of the drone sighting. Once the Captain was able to finally ask for clarification the controller issued a climb to FL230 and stated 'you're not going to make that climb restriction here's the number to call for a pilot deviation.' We were still at 12000 ft and approximately 17 NM from the 15000 ft or above restriction at DOTSS when he made that pronouncement. We ended up crossing DOTSS at approximately 17000 ft.After speaking with a supervisor at the SoCal ATC faculty; it seems the controller was a bit task saturated with the drone in the area and coordinating with other aircraft. He also stated there was no violation.

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.