Narrative:

We were on the initial climb out taking off [runway] 31 at lga with right turn (rt) 360 on the LGA5 SID; white first fix. Shortly after the right turn 360 we were cleared further rt 220 and climb to 7000. As we reached 6000 we were cleared to 12000'. ATC also called for VFR traffic at 7;500' that we observed on TCAS. While the captain/pilot monitoring (pm) was looking for traffic at 7000'; I responded to a TCAS RA to level off. I complied with the level off RA command by leveling off and rolling out of the bank to follow the flight director guidance. We were in climb power setting when I rapidly leveled off to follow the TCAS RA and I didn't override the auto throttle (a/T) fast enough and airspeed read 275KT IAS for a brief moment before I overrode the a/T to reduce speed back to 250 KT IAS. The pm properly communicated that we were responding to an RA but didn't have an opportunity to call out my deviation and I called for correcting airspeed when I caught the airspeed deviation after responding to the RA.the pm was looking for traffic while I was responding to the RA; I focused on the flight director and decreased my scan and for a brief moment and let airspeed increase. I didn't exceed aircraft limitation but let airspeed increase beyond airspace restriction of 250 below 10;000. As the pm was busy looking for traffic he was not able to call my deviation. I made the mistake of over relying on automation in this event. I should have anticipated the a/T lag and manually reduced power in the rapid level off.I believe that with more experience; I would have reduced power at the same time that I leveled off when responding to the RA command. I am now more aware of the a/T lag to adjust power settings.

Google
 

Original NASA ASRS Text

Title: First Officer reported exceeding 250kts below 10;000'; while complying with a TCAS resolution advisory.

Narrative: We were on the initial climb out taking off [runway] 31 at LGA with Right Turn (RT) 360 on the LGA5 SID; WHITE First fix. Shortly after the right turn 360 we were cleared further RT 220 and climb to 7000. As we reached 6000 we were cleared to 12000'. ATC also called for VFR traffic at 7;500' that we observed on TCAS. While the Captain/Pilot Monitoring (PM) was looking for traffic at 7000'; I responded to a TCAS RA to level off. I complied with the level off RA command by leveling off and rolling out of the bank to follow the Flight Director guidance. We were in climb power setting when I rapidly leveled off to follow the TCAS RA and I didn't override the auto throttle (A/T) fast enough and airspeed read 275KT IAS for a brief moment before I overrode the A/T to reduce speed back to 250 KT IAS. The PM properly communicated that we were responding to an RA but didn't have an opportunity to call out my deviation and I called for correcting airspeed when I caught the airspeed deviation after responding to the RA.The PM was looking for traffic while I was responding to the RA; I focused on the flight director and decreased my scan and for a brief moment and let airspeed increase. I didn't exceed aircraft limitation but let airspeed increase beyond airspace restriction of 250 below 10;000. As the PM was busy looking for traffic he was not able to call my deviation. I made the mistake of over relying on automation in this event. I should have anticipated the A/T lag and manually reduced power in the rapid level off.I believe that with more experience; I would have reduced power at the same time that I leveled off when responding to the RA command. I am now more aware of the A/T lag to adjust power settings.

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.