37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1740373 |
Time | |
Date | 202004 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
During our flight from ZZZ1-ZZZ we were cleared to descend via the zzzzz arrival into ZZZ1. Due to the coronavirus there was a logistical situation developing at our destination that ultimately resulted in our being stuck at the destination without transportation; and me and the captain were actively engaged in conversation trying to solve that issue. The bottom of the descent on the zzzzz arrival is 11;000 feet. The aircraft had leveled at 11;000 feet and then a short while later I noticed the vertical path indicator descending indicating we were passing through the descent point for the proper descent path. Due to being focused on the conversation at hand; I was confused as to the state of the aircraft on the arrival. I had lost situational awareness to the fact the aircraft had already leveled at the bottom of the arrival and assumed we still had more altitude to lose. I questioned the situation asking the pm what the deal was and why we were not descending. The pm was trying to determine the issue and at that point I initiated a descent. Almost immediately we both realized that the aircraft had been level at the correct and final altitude on the arrival and I immediately initiated a climb back to 11;000 feet; which was our clearance limit. Unfortunately; we had descended to 10;500 feet during the process.after the fact we realized that the issue happened because the pm had put a crossing altitude at the airport for planning purposes and that was generating the vertical guidance that caught my attention and caused me to get confused. We had not discussed the altitude put in at the airport yet due to the discussion pertaining to the logistics developing at the destination. The issue was completely my fault. I should not have initiated a descent without first confirming the state of the aircraft on the arrival. In the attempt to keep from getting high; I caused us to actually get too low. This is also a good reminder to deal with ground issues on the ground or in downtime during cruise; and not during the arrival or later phases of flight. We were not in sterile cockpit but it was not the right time to be dealing with the logistic problems; at least not the PF!going forward; coronavirus or not; I have to focus on the appropriate phase of flight and not get distracted by issues on the ground while in critical phases of flight; like the arrival.
Original NASA ASRS Text
Title: Corporate First Officer reported descending prior to a crossing restriction during arrival. First Officer referenced being distracted talking about COVID-19 related logistical issues that may have contributed to the event.
Narrative: During our flight from ZZZ1-ZZZ we were cleared to descend via the ZZZZZ Arrival into ZZZ1. Due to the Coronavirus there was a logistical situation developing at our destination that ultimately resulted in our being stuck at the destination without transportation; and me and the Captain were actively engaged in conversation trying to solve that issue. The bottom of the descent on the ZZZZZ Arrival is 11;000 feet. The aircraft had leveled at 11;000 feet and then a short while later I noticed the vertical path indicator descending indicating we were passing through the descent point for the proper descent path. Due to being focused on the conversation at hand; I was confused as to the state of the aircraft on the arrival. I had lost situational awareness to the fact the aircraft had already leveled at the bottom of the arrival and assumed we still had more altitude to lose. I questioned the situation asking the PM what the deal was and why we were not descending. The PM was trying to determine the issue and at that point I initiated a descent. Almost immediately we both realized that the aircraft had been level at the correct and final altitude on the arrival and I immediately initiated a climb back to 11;000 feet; which was our clearance limit. Unfortunately; we had descended to 10;500 feet during the process.After the fact we realized that the issue happened because the PM had put a crossing altitude at the airport for planning purposes and that was generating the vertical guidance that caught my attention and caused me to get confused. We had not discussed the altitude put in at the airport yet due to the discussion pertaining to the logistics developing at the destination. The issue was completely my fault. I should not have initiated a descent without first confirming the state of the aircraft on the arrival. In the attempt to keep from getting high; I caused us to actually get too low. This is also a good reminder to deal with ground issues on the ground or in downtime during cruise; and not during the arrival or later phases of flight. We were not in sterile cockpit but it was not the right time to be dealing with the logistic problems; at least not the PF!Going forward; Coronavirus or not; I have to focus on the appropriate phase of flight and not get distracted by issues on the ground while in critical phases of flight; like the arrival.
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.