Gsp TRACON controller reported they allowed an IFR emergency aircraft to fly below the minimum vecto...

Narrative:

I received a briefing for the radar position. In the briefing; I was told that aircraft X was landing at gmu and was already talking to gmu tower and a king air was also on their frequency. A minute or two later gmu calls and informs me that aircraft X was having gear issues; but did not want to cancel his IFR. He just wanted to go out and try to hand crank his landing gear in an attempt to make it work. I then asked if the aircraft wanted to come back out to approach or stay with the tower. Gmu advised that the aircraft didn't really want to go back out to approach frequency so I said that he was their control for anything that they needed. At that point the previous controller coordinated with gmu that the king air had never been IFR that he was VFR the whole time he had worked him. I heard the coordination and assumed he was referencing aircraft X since there was no reason to be talking about the king air. Aircraft X eventually started going west bound into a 3500 foot minimum vectoring altitude at 3000 feet. I did not believe this was an issue since I thought he was VFR and gmu was just confused about his status earlier. The aircraft eventually landed without incident. Upon arriving to work the next morning I was told that the aircraft was not VFR; but was IFR during the entire emergency. I have no real recommendations as it was just a very unique situation with the emergency and confusion about the IFR/VFR status of the plane. I should have verified if there was ever any question of his status.

Original NASA ASRS Text

Title: GSP TRACON Controller reported they allowed an IFR emergency aircraft to fly below the Minimum Vectoring Altitude because they believed the aircraft was VFR.

Narrative: I received a briefing for the radar position. In the briefing; I was told that Aircraft X was landing at GMU and was already talking to GMU Tower and a King Air was also on their frequency. A minute or two later GMU calls and informs me that Aircraft X was having gear issues; but did not want to cancel his IFR. He just wanted to go out and try to hand crank his landing gear in an attempt to make it work. I then asked if the aircraft wanted to come back out to Approach or stay with the Tower. GMU advised that the aircraft didn't really want to go back out to Approach frequency so I said that he was their control for anything that they needed. At that point the previous Controller coordinated with GMU that the King Air had never been IFR that he was VFR the whole time he had worked him. I heard the coordination and assumed he was referencing Aircraft X since there was no reason to be talking about the King Air. Aircraft X eventually started going west bound into a 3500 foot Minimum Vectoring Altitude at 3000 feet. I did not believe this was an issue since I thought he was VFR and GMU was just confused about his status earlier. The aircraft eventually landed without incident. Upon arriving to work the next morning I was told that the aircraft was not VFR; but was IFR during the entire emergency. I have no real recommendations as it was just a very unique situation with the emergency and confusion about the IFR/VFR status of the plane. I should have verified if there was ever any question of his status.

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	1650211
Time
Date	201905
Local Time Of Day	1801-2400
Place
Locale Reference	GMU.Airport
State Reference	SC
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Baron 58/58TC
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Component
Aircraft Component	Landing Gear
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 4
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT

Gsp TRACON controller reported they allowed an IFR emergency aircraft to fly below the minimum vectoring altitude because they believed the aircraft was VFR.