Boston approach controller reported they did not climb an aircraft on an IFR flight plan because the...

Narrative:

I had taken the position a few minutes prior and was briefed that aircraft X was on an approach and had another approach request at a different airport. The weather was good VFR; and I was working both a feeder sector and the south satellite sector. When aircraft X departed after the practice approach I radar identify the aircraft and verified his next approach request. This entire time; for some unknown reason; I did not realize that aircraft X was on an IFR flight plan. I somehow assumed that with the good weather and the multiple approach requests that the aircraft was VFR. In thinking this I initiated a hand off to the next sector and issued a frequency change. I did not turn; climb or clear the aircraft to his next destination; again; because I was thinking the aircraft was VFR. My lack of action resulted in the aircraft being level at 2;000 feet in; or about to enter; an area with a 2;400 foot MVA (minimum vectoring area). The controller of the receiving sector noticed this and initiated a turn and eventual climb and alerted me to the situation. As soon as I took the position my attention was focused on my feed to the final controller; as all of my aircraft had to be taken off the STAR to create the room final needed as we were only able to land one runway at the time and not the usual two. The short story is I did not recognize the control status that aircraft X was under and failed to take appropriate action as a result. This event occurred because I did not have a thorough understanding of the traffic at the time I took the position. I need to take the extra few seconds in my pre-brief in the future to grasp this.

Original NASA ASRS Text

Title: Boston Approach Controller reported they did not climb an aircraft on an IFR flight plan because they thought the aircraft was on a VFR flight and the aircraft flew below the Minimum Vectoring Altitude.

Narrative: I had taken the position a few minutes prior and was briefed that Aircraft X was on an approach and had another approach request at a different airport. The weather was good VFR; and I was working both a feeder sector and the south satellite sector. When Aircraft X departed after the practice approach I radar identify the aircraft and verified his next approach request. This entire time; for some unknown reason; I did not realize that Aircraft X was on an IFR flight plan. I somehow assumed that with the good weather and the multiple approach requests that the aircraft was VFR. In thinking this I initiated a hand off to the next sector and issued a frequency change. I did not turn; climb or clear the aircraft to his next destination; again; because I was thinking the aircraft was VFR. My lack of action resulted in the aircraft being level at 2;000 feet in; or about to enter; an area with a 2;400 foot MVA (Minimum Vectoring Area). The controller of the receiving sector noticed this and initiated a turn and eventual climb and alerted me to the situation. As soon as I took the position my attention was focused on my feed to the final controller; as all of my aircraft had to be taken off the STAR to create the room final needed as we were only able to land one runway at the time and not the usual two. The short story is I did not recognize the control status that Aircraft X was under and failed to take appropriate action as a result. This event occurred because I did not have a thorough understanding of the traffic at the time I took the position. I need to take the extra few seconds in my pre-brief in the future to grasp this.

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	1652663
Time
Date	201906
Local Time Of Day	1801-2400
Place
Locale Reference	A90.TRACON
State Reference	MA
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	Helicopter
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Other Instrument Approach
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 0.5
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT

Boston approach controller reported they did not climb an aircraft on an IFR flight plan because they thought the aircraft was on a VFR flight and the aircraft flew below the minimum vectoring altitude.