Date: 201605
Local time of day: 1201-1800
Location: DLH.TRACON, MN
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class E DLH
ATC / advisory: TRACON DLH
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Developmental
Human factors: Situational Awareness; Communication Breakdown
Second reporter function: Supervisor / CIC
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure; Human Factors; Chart Or Publication
Primary problem: Chart Or Publication

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.


Second narrative: I was giving a certification skill check on Arrival Data. The Radar Controller was vectoring Aircraft X for the ILS Approach. All seemed normal; and then after the aircraft was on about a 5 mile final; the Tower controller called down to ask us if we had the NOTAM for the mining blast. The controller stated that they did not have the information and as soon as we got the information; the aircraft was already in the TFR. The blast was a FDC NOTAM that comes on a fax paper days ahead of time. It then gets put up on the Controller In Charge console in the tower. When the TRACON opened in the morning; the TRACON controller calls up to Flight Data and asks for a Status Area Board (SIA) check. This was completed. NOTAMS are not always accurate on our SIA. Flight Service calls with some of the NOTAMs but doesn't always cancel them. MOCC calls with NOTAMs; we receive faxes from ARTCC with NOTAMS. There is no one place for NOTAMs. I recommend that we do a morning check on pilotweb for current NOTAMS; but that doesn't help for NOTAMS that appear during the day. Also; if our IDS system would get up and running; controllers would have access to up-to-date information on NOTAMS for each airport we control. Another problem area is that TFR NOTAMS get put under the center's NOTAM page. These blast NOTAMs wouldn't show up under the airport. This NOTAM was 12 miles northwest of the VOR which is 6 miles northwest of the airport. Pilots pulling up NOTAMS would never know this exists. A change needs to be made to how the NOTAMS appear for each pilot and controller so that it is useful.


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