Date: 201310
Local time of day: 0001-0600
Location: ZMP.ARTCC, MN
Aircraft: EMB ERJ 135 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class E RST
ATC / advisory: Center ZMP
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Other / Unknown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: RST Approach normally operates from 0500-2300 local time; and ZMP Sector 07 controls the airspace when they are closed. Very close to closing; an E135 was being vectored around RST airport for a landing with numerous thunderstorms in the vicinity. The aircraft was about 4-5 miles northeast of the airfield turned on a 310 heading and descending to 040. RST Approach was currently working the aircraft and had assigned the heading and altitude. The RST Approach Controller then called me to give me control of the airspace but had not assured the aircraft could make it to the airport for an approach. They also informed me there were numerous thunderstorms in the area. The RST Controller asked me if I wanted to vector the aircraft myself or be given direct the IAF to fly the full approach. With thunderstorms surrounding the airfield; I chose to vector the aircraft myself. However; at 2300; many of the sectors in the area are combined and we work on a larger RADAR range; which makes it a little more difficult to vector for approach. Also; the radio frequency is not as strong at RST for when the pilot can radio us when they are safely on the ground. I vectored the aircraft and it did make a safe landing using the ILS 13 approach; but did say the weather was pretty rough on the way in. I understand that RST airspace closes at 2300 local time; but I am fairly certain that a controller is staffed at RST until at least 2315. In the scenario above; the aircraft was not more than 5 minutes of being established on the approach and landing. RST has a much better RADAR for vectoring close to the airport plus they have the added advantage of seeing out the Tower Cab and seeing the weather directly on the field. The Controller could have kept the airspace for a few more minutes to assure that the aircraft made it safely to the airfield. Even if they want to give us the airspace; then maybe the Controller can stay in the Tower; operating as a VFR Tower; to assure a safe landing. When we take the airspace we don't know if the Tower is currently occupied; if anything happens to the aircraft we won't know if they made it to the field. If an accident had occurred around the airport; we would have had to wait the full 30 minutes without a report before sending out Search and Rescue (SAR). I would recommend that in a situation where an aircraft is within 5 minutes or 5 miles of RST when the airspace is closing; that they remain open and then hand us the airspace after the aircraft has made a safe landing. Or make sure the aircraft is established on a approach; hand the airspace over to ZMP; but remain open as a VFR Tower until the aircraft lands safely at the airport The airspace may be open slightly after 2300; but open a few minutes later to help aircraft safely navigate weather and arrive safely at the airport would be much more beneficial to the NAS then having a Controller stay open a few minutes later.




Synopsis: ZMP Controller described an unsafe condition involving the closure of RST Approach and the need to vector an inbound aircraft through weather. Reporter suggested the Approach Control be kept open for a few minutes to provide improved service to late arrivals.