 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
TRACON controller reported an airborne conflict and attributed it to staffing levels due to the covid-19 pandemic.
| Attributes | |
| ACN | 1744042 |
| Time | |
| Date | 202005 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.TRACON |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Descent |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Descent |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute Departure Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Conflict Airborne Conflict |
Narrative:
I was working the satellite sector. I had several aircraft in my airspace on two frequencies and constant shout line communication. I was delivering aircraft to the adjacent sector at even altitudes (correct direction of flight). ZZZ tower tagged and coordinated a VFR aircraft with an alternator issue as what I deemed could be a possible emergency; but I was not in communication with the aircraft. A separate target not tagged indicated 4;000 feet. To prevent a possible conflict I climbed the multiple aircraft I was delivering to 6;000. This altered the altitude we usually deliver aircraft in that sector. I received a arrival to ZZZ at 5;000; knowing I would have to separate my arrival from the aircraft with the alternator issue not on frequency I started the aircraft decent earlier than usual. I cleared the ZZZ arrival aircraft to zzzzz; the initial approach fix. I descended an arrival aircraft to runway X based on the lateral course zzzzz offered. The aircraft made a very slow course to zzzzz. Realizing the conflict I issued heading to diverge the courses. Shoutline; multiple frequencies; workload and reduced staffing all played a role in this error. With reduced staffing during this pandemic; we are working with less of the manpower we are normally afforded. While commercial traffic is down general aviation has remained solid. We need to staff based on the demand.
Original NASA ASRS Text
Title: TRACON Controller reported an airborne conflict and attributed it to staffing levels due to the COVID-19 pandemic.
Narrative: I was working the Satellite sector. I had several aircraft in my airspace on two frequencies and constant shout line communication. I was delivering aircraft to the adjacent sector at even altitudes (correct direction of flight). ZZZ Tower tagged and coordinated a VFR aircraft with an alternator issue as what I deemed could be a possible emergency; but I was not in communication with the aircraft. A separate target not tagged indicated 4;000 feet. To prevent a possible conflict I climbed the multiple aircraft I was delivering to 6;000. This altered the altitude we usually deliver aircraft in that sector. I received a arrival to ZZZ at 5;000; knowing I would have to separate my arrival from the aircraft with the alternator issue not on frequency I started the aircraft decent earlier than usual. I cleared the ZZZ arrival aircraft to ZZZZZ; the initial approach fix. I descended an arrival aircraft to Runway X based on the lateral course ZZZZZ offered. The aircraft made a very slow course to ZZZZZ. Realizing the conflict I issued heading to diverge the courses. Shoutline; multiple frequencies; workload and reduced staffing all played a role in this error. With reduced staffing during this pandemic; we are working with less of the manpower we are normally afforded. While commercial traffic is down general aviation has remained solid. We need to staff based on the demand.
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.