37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1368644 |
Time | |
Date | 201607 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Altitude Undershoot Deviation - Procedural Clearance |
Narrative:
We were given a climb clearance to FL360 from the previous controller who had us on a vector for traffic. He then cleared us back direct to intersection zzzzz passing FL320. We received a frequency change passing FL330. After checking in with him; he advised us that we would have to be level in 2 1/2 minutes. At the time we did not see a problem complying with the restriction. About this time we received a company message telling us that our return flight was going to have to land at [a different airport] to clear customs because of the late departure that was expected. At the 2 1/2 minute point we were passing FL355 and the controller asked us to turn 15 degrees left for traffic. We saw the traffic visually and also on TCAS. We did not receive any TA or RA for the traffic. Once level at FL360 he then cleared us back to zzzzz. No comment was made about the event from the controller so we decided to file the as soon as possible to emphasize how easily a distraction can take you out of the green.this event occurred mainly because of the distraction from the received company message. We were trying to respond to him via ACARS and became distracted from the compliance with the climb instructions which we originally thought would be made easily; but since the climb rate had slowed up more than expected; we ended up being about 500 feet low.
Original NASA ASRS Text
Title: During climb in an A320 in contact with ATC controllers for vectors for traffic and clearance for flight levels; the flight crew was distracted by a company message via ACARS about a return flight causing a slowing of the climb rate.
Narrative: We were given a climb clearance to FL360 from the previous controller who had us on a vector for traffic. He then cleared us back direct to intersection ZZZZZ passing FL320. We received a frequency change passing FL330. After checking in with him; he advised us that we would have to be level in 2 1/2 minutes. At the time we did not see a problem complying with the restriction. About this time we received a company message telling us that our return flight was going to have to land at [a different airport] to clear customs because of the late departure that was expected. At the 2 1/2 minute point we were passing FL355 and the controller asked us to turn 15 degrees left for traffic. We saw the traffic visually and also on TCAS. We did not receive any TA or RA for the traffic. Once level at FL360 he then cleared us back to ZZZZZ. No comment was made about the event from the controller so we decided to file the ASAP to emphasize how easily a distraction can take you out of the green.This event occurred mainly because of the distraction from the received company message. We were trying to respond to him via ACARS and became distracted from the compliance with the climb instructions which we originally thought would be made easily; but since the climb rate had slowed up more than expected; we ended up being about 500 feet low.
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.