Dlh TRACON controllers reported not being aware of a tfr and vectoring an aircraft through it. A con...

Attributes
ACN	1358140
Time
Date	201605
Local Time Of Day	1201-1800
Place
Locale Reference	DLH.TRACON
State Reference	MN
Environment
Light	Daylight
Aircraft 1
Make Model Name	Light Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Developmental
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 1
Person 2
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 15.1
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy

Narrative:

I was working R2 position in the TRACON. Aircraft X came from the east descending to 13000 ft. I advised them to continue descent to 4000 ft and advise what approach requesting. Aircraft X requested vector to ZZZ. After assuring aircraft X; had NOTAM at ZZZ and called ahead for their arrival. I vectored aircraft X to the north on a downwind leg. Vectored the aircraft and cleared them for the approach. On a 5 mile final local called down to arrival data to check if we had the tfr that begin 13 minutes earlier. There was no record of the blast in the TRACON. The aircraft was changed to advisory already when it was noticed they had flown through the tfr. Aircraft cancelled IFR a few minutes later.when the TRACON was opened the tfr was never passed. Notams and tfrs need to be checked regularly and passed.

Original NASA ASRS Text

Title: DLH TRACON controllers reported not being aware of a TFR and vectoring an aircraft through it. A contributing factor included how NOTAMs are distributed.

Narrative: I was working R2 position in the TRACON. Aircraft X came from the east descending to 13000 ft. I advised them to continue descent to 4000 ft and advise what approach requesting. Aircraft X requested vector to ZZZ. After assuring Aircraft X; had NOTAM at ZZZ and called ahead for their arrival. I vectored Aircraft X to the north on a downwind leg. Vectored the aircraft and cleared them for the approach. On a 5 mile final local called down to arrival data to check if we had the TFR that begin 13 minutes earlier. There was no record of the blast in the TRACON. The aircraft was changed to advisory already when it was noticed they had flown through the TFR. Aircraft cancelled IFR a few minutes later.When the TRACON was opened the TFR was never passed. NOTAMs and TFRs need to be checked regularly and passed.

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.

Dlh TRACON controllers reported not being aware of a tfr and vectoring an aircraft through it. A contributing factor included how notams are distributed.