Hcf controller reported a possible missed altitude readback from an A321 flight crew resulted in des...

Narrative:

I noticed aircraft X was establishing himself on the localizer at 2;000. The minimum safe altitude for the localizer is 3;000. I told aircraft X that minimum safe altitude was 3;000 and climbed him back to 3;000. Aircraft X stated I told him 2;000. I don't believe I cleared him at 2;000; but I didn't want to argue with him on frequency; so I just climbed him back up. I still believe I had him join at 3;000; but I haven't heard the tapes so I can't be sure. If he did read back 2;000 instead of 3;000; I was probably just fatigued.if this is a hearback/readback issue; I blame the short staffing at the hcf. I am fatigued; as are my coworkers. I am on the no list for overtime; but I was forced to stay an extra two hours and work a ten hour day; the date of this incident. I honestly believe if the facility were staffed properly; the controllers would be better rested and better able to control traffic. On the night in question; management staffed a d-side only as a controller; but she was limited to where and what times she can work; so this caused long periods on position for all of the controllers. Fatigue is playing a factor in our day-to-day operations. I hope that management will staff overtime (an 8 hour person versus just holding over a person already working 8 hours; to make it a 10 hour day) during rimpac because I fear a catastrophic incident could potentially happen.

Original NASA ASRS Text

Title: HCF Controller reported a possible missed altitude readback from an A321 flight crew resulted in descent below the MVA. Staffing and fatigue were cited as contributing factors.

Narrative: I noticed Aircraft X was establishing himself on the localizer at 2;000. The minimum safe altitude for the localizer is 3;000. I told Aircraft X that minimum safe altitude was 3;000 and climbed him back to 3;000. Aircraft X stated I told him 2;000. I don't believe I cleared him at 2;000; but I didn't want to argue with him on frequency; so I just climbed him back up. I still believe I had him join at 3;000; but I haven't heard the tapes so I can't be sure. If he did read back 2;000 instead of 3;000; I was probably just fatigued.If this is a hearback/readback issue; I blame the short staffing at the HCF. I am fatigued; as are my coworkers. I am on the no list for overtime; but I was forced to stay an extra two hours and work a ten hour day; the date of this incident. I honestly believe if the facility were staffed properly; the controllers would be better rested and better able to control traffic. On the night in question; management staffed a D-Side only as a controller; but she was limited to where and what times she can work; so this caused long periods on position for all of the controllers. Fatigue is playing a factor in our day-to-day operations. I hope that management will staff overtime (an 8 hour person versus just holding over a person already working 8 hours; to make it a 10 hour day) during RIMPAC because I fear a catastrophic incident could potentially happen.

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.

Attributes
ACN	1550479
Time
Date	201806
Local Time Of Day	0001-0600
Place
Locale Reference	HCF.TRACON
State Reference	HI
Environment
Light	Night
Aircraft 1
Make Model Name	A321
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT

Hcf controller reported a possible missed altitude readback from an A321 flight crew resulted in descent below the MVA. Staffing and fatigue were cited as contributing factors.