Narrative:

The error sequence began when I accepted a handoff from ZBW flight planned kempe; hedux; lkp. I asked the aircraft if they would prefer to go direct hedux for straight-in RNAV-a from their present position -- 14 NM southeast of hedux. I issued a clearance to cross hedux at 5200 ft (MVA east of hedux) cleared straight-in RNAV-a approach. When the aircraft was at hedux at 5200 ft; I had xferred communication to ZBW. (ZBW is the control facility for lkp; although this approach is within btv airspace.) I realized; as the aircraft crossed hedux he was below the required altitudes for the approach. The approach crosses mountainous terrain. I immediately contacted ZBW and advised them of my error; for which they issued corrective instructions to the aircraft. Factors: I was the watch 'controller in charge.' I was involved directly; via phone line; with coordinating the relief of tower controllers for the end of their shift. Note: the facility manager had been assisting us through the day. At the time he returned to his office; I was on radar approach control. The other controller assigned to the TRACON; was working flight data/assist. Traffic was a factor. In addition to normal IFR/VFR operations; there was parachute jumping in the airspace; and 3 flts of F-16's departed. 2 flts immediately canceled IFR and proceeded to depart our airspace and immediately re-entered the airspace on VR1800 at 440 KTS with traffic ahead; on their route of flight. I physically held the lkp RNAV-a approach plate in my hand. I failed to verify the altitudes required to complete the approach. The manager was advised and the incident is being investigated. MSAW did not activate for this aircraft; but did activate for VR1800 traffic.

Related reports:

Google
 

Original NASA ASRS Text

Title: BTV CTLR EXPERIENCED OPERROR WHEN ISSUING A 5200 FT XING ALT AT HEDUX FOR RNAV-A (GPS) TO LKP.

Narrative: THE ERROR SEQUENCE BEGAN WHEN I ACCEPTED A HDOF FROM ZBW FLT PLANNED KEMPE; HEDUX; LKP. I ASKED THE ACFT IF THEY WOULD PREFER TO GO DIRECT HEDUX FOR STRAIGHT-IN RNAV-A FROM THEIR PRESENT POS -- 14 NM SE OF HEDUX. I ISSUED A CLRNC TO CROSS HEDUX AT 5200 FT (MVA E OF HEDUX) CLRED STRAIGHT-IN RNAV-A APCH. WHEN THE ACFT WAS AT HEDUX AT 5200 FT; I HAD XFERRED COM TO ZBW. (ZBW IS THE CTL FACILITY FOR LKP; ALTHOUGH THIS APCH IS WITHIN BTV AIRSPACE.) I REALIZED; AS THE ACFT CROSSED HEDUX HE WAS BELOW THE REQUIRED ALTS FOR THE APCH. THE APCH CROSSES MOUNTAINOUS TERRAIN. I IMMEDIATELY CONTACTED ZBW AND ADVISED THEM OF MY ERROR; FOR WHICH THEY ISSUED CORRECTIVE INSTRUCTIONS TO THE ACFT. FACTORS: I WAS THE WATCH 'CTLR IN CHARGE.' I WAS INVOLVED DIRECTLY; VIA PHONE LINE; WITH COORDINATING THE RELIEF OF TWR CTLRS FOR THE END OF THEIR SHIFT. NOTE: THE FACILITY MGR HAD BEEN ASSISTING US THROUGH THE DAY. AT THE TIME HE RETURNED TO HIS OFFICE; I WAS ON RADAR APCH CTL. THE OTHER CTLR ASSIGNED TO THE TRACON; WAS WORKING FLT DATA/ASSIST. TFC WAS A FACTOR. IN ADDITION TO NORMAL IFR/VFR OPS; THERE WAS PARACHUTE JUMPING IN THE AIRSPACE; AND 3 FLTS OF F-16'S DEPARTED. 2 FLTS IMMEDIATELY CANCELED IFR AND PROCEEDED TO DEPART OUR AIRSPACE AND IMMEDIATELY RE-ENTERED THE AIRSPACE ON VR1800 AT 440 KTS WITH TFC AHEAD; ON THEIR RTE OF FLT. I PHYSICALLY HELD THE LKP RNAV-A APCH PLATE IN MY HAND. I FAILED TO VERIFY THE ALTS REQUIRED TO COMPLETE THE APCH. THE MGR WAS ADVISED AND THE INCIDENT IS BEING INVESTIGATED. MSAW DID NOT ACTIVATE FOR THIS ACFT; BUT DID ACTIVATE FOR VR1800 TFC.

Data retrieved from NASA's ASRS site as of January 2009 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.