37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1739613 |
Time | |
Date | 202004 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Type 161 |
Person 2 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 19 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Unstabilized Approach |
Narrative:
I am submitting this safety report to highlight a growing challenging environment with covid-19 and related training and currency issues. On the flight I flew to ZZZ yesterday; I was paired with a new first officer who is on an extension trying to consolidate and hasn't been flying as a reserve. He reportedly has been trying to get flying and has been unable. I also have not been flying much with reserve and 'bunky' trips. My last 'assignment' was a landing class in ZZZ1. For our trip yesterday; we were scheduled to fly ZZZ2-ZZZ-ZZZ2. Being new and having less than 100 hours; the first officer couldn't takeoff or land in ZZZ2; so I decided that I'd fly to cruise; let the first officer fly enroute and descent to ZZZ; and then reverse that returning so he could gather some experience. With ZZZ being a new airport for both of us; and with non-precision approaches in use; that wasn't my first choice (I had intended to fly into ZZZ); but I didn't want to take both legs and not give the first officer an opportunity to fly. With the inexperience of the first officer and both of our currency issues; my brief then included the request that we definitely watch one another and work together as a team. Our flight worked that way on departure and enroute; but then became somewhat challenging for both of us going into ZZZ. The weather was overcast in light rain and the RNAV approach to [runway] xx was in use. Prior to descent; the first officer conducted a thorough brief and reviewed/briefed the RNAV approach procedures from the approach briefing guide. All then went well until we were vectored toward the final course just outside zzzzz fix; told to maintain 5;000 until established; and cleared for the approach. We were then very careful setting up everything for the rarely conducted RNAV approach per SOP. The problem however was that our vector by ATC was poor and we didn't intercept until just slightly outside zzzzz which is normally crossed at 4;300 feet. With a combination of being focused on the RNAV procedures; ATC communications (controller realized at the last minute that his vector had been poor); and honestly some rustiness on my part; I didn't immediately recognize that we were high until we broke through the clouds just outside zzzzz and I saw the runway. The first officer then immediately disconnected the autopilot in visual conditions; added additional drag and was able to salvage the approach to a safe landing. It worked out; but the approach and descent was obviously not as well conducted as either of us would have preferred.
Original NASA ASRS Text
Title: Air carrier flight crew reported conducting an unstable approach to a landing into an unfamiliar airport. The crew cited flying frequency as the main cause attributed to a reduction of flights during the COVID-19 pandemic.
Narrative: I am submitting this safety report to highlight a growing challenging environment with COVID-19 and related training and currency issues. On the flight I flew to ZZZ yesterday; I was paired with a new FO who is on an extension trying to consolidate and hasn't been flying as a reserve. He reportedly has been trying to get flying and has been unable. I also have not been flying much with reserve and 'bunky' trips. My last 'assignment' was a landing class in ZZZ1. For our trip yesterday; we were scheduled to fly ZZZ2-ZZZ-ZZZ2. Being new and having less than 100 hours; the FO couldn't takeoff or land in ZZZ2; so I decided that I'd fly to cruise; let the FO fly enroute and descent to ZZZ; and then reverse that returning so he could gather some experience. With ZZZ being a new airport for both of us; and with non-precision approaches in use; that wasn't my first choice (I had intended to fly into ZZZ); but I didn't want to take both legs and not give the FO an opportunity to fly. With the inexperience of the FO and both of our currency issues; my brief then included the request that we definitely watch one another and work together as a team. Our flight worked that way on departure and enroute; but then became somewhat challenging for both of us going into ZZZ. The weather was overcast in light rain and the RNAV approach to [Runway] XX was in use. Prior to descent; the FO conducted a thorough brief and reviewed/briefed the RNAV approach procedures from the Approach Briefing Guide. All then went well until we were vectored toward the final course just outside ZZZZZ fix; told to maintain 5;000 until established; and cleared for the approach. We were then very careful setting up everything for the rarely conducted RNAV approach per SOP. The problem however was that our vector by ATC was poor and we didn't intercept until just slightly outside ZZZZZ which is normally crossed at 4;300 feet. With a combination of being focused on the RNAV procedures; ATC communications (Controller realized at the last minute that his vector had been poor); and honestly some rustiness on my part; I didn't immediately recognize that we were high until we broke through the clouds just outside ZZZZZ and I saw the runway. The FO then immediately disconnected the autopilot in visual conditions; added additional drag and was able to salvage the approach to a safe landing. It worked out; but the approach and descent was obviously not as well conducted as either of us would have preferred.
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.