Narrative:

Sector R13 had an airspace deviation into my airspace; sector R34. Aircraft X entered my airspace without a handoff; for approximately 4;000 ft or 5 minutes. I was not busy at all at the time; but the [sector] 13 controller was very busy. This event happened because the lack of currency and proficiency that the R13 controller had. He is a person that is only required to get 8 hour/month of currency time; and his traffic complexity far exceeded his capabilities. Additionally; he is not trained correctly. I split off R34 (FL370 and up); over top of R13; and when I called him for a briefing; and he did not know what R34 was; what altitudes it had; or even the sector name. It was obvious he was not trained correctly. Additionally; R13 was a red sector; without a d-side at the time (a d-side was called later); and eventually he deviated my airspace because of lack of currency. When the deviation occurred; he did not have a d-side; and his rides were bad so he had a lot of pilot requests.controllers that get the bare-minimum 8 hour/month should not be allowed to work a 'red' sector; nor a 'yellow' sector; without a d-side. Calling people to help area 1; with its low staffing issues; with people that only get the bare minimum currency hours is not a safe practice. I've reported this issue before; and it continues to be an issue. These people; eventually; due to lack of ability; lack of experience; and lack of currency; hurt the area and cause unsafe situations. This is just one example; but I'll be filing more reports when I see it. Covering up staffing issues with non-experienced cpc's is not a good idea. Area 1 needs to use and/or schedule overtime for personnel willing to work it during the busy season (summer); that have plenty of currency hours and recent experience; this is no different from operating an aircraft!

Related reports:

Google
 

Original NASA ASRS Text

Title: ZMP Controller describes an airspace violation in his airspace; caused by a staff specialist.

Narrative: Sector R13 had an airspace deviation into my airspace; Sector R34. Aircraft X entered my airspace without a handoff; for approximately 4;000 FT or 5 minutes. I was not busy at all at the time; but the [Sector] 13 Controller was very busy. This event happened because the lack of currency and proficiency that the R13 Controller had. He is a person that is only required to get 8 hour/month of currency time; and his traffic complexity FAR exceeded his capabilities. Additionally; he is not trained correctly. I split off R34 (FL370 and up); over top of R13; and when I called him for a briefing; and he did not know what R34 was; what altitudes it had; or even the sector name. It was obvious he was not trained correctly. Additionally; R13 was a RED sector; without a D-Side at the time (a D-Side was called later); and eventually he deviated my airspace because of lack of currency. When the deviation occurred; he did not have a D-Side; and his rides were bad so he had a lot of pilot requests.Controllers that get the bare-minimum 8 hour/month should not be allowed to work a 'red' sector; nor a 'yellow' sector; without a D-Side. Calling people to help Area 1; with its low staffing issues; with people that only get the bare minimum currency hours is not a safe practice. I've reported this issue before; and it continues to be an issue. These people; eventually; due to lack of ability; lack of experience; and lack of currency; hurt the area and cause unsafe situations. This is just one example; but I'll be filing more reports when I see it. Covering up staffing issues with non-experienced CPC's is not a good idea. Area 1 needs to use and/or schedule overtime for personnel willing to work it during the busy season (summer); that have plenty of currency hours and recent experience; this is no different from operating an aircraft!

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.