PA34 PLT INADVERTENTLY ENTERS A TFR DURING A CONTRACTED FLT IN THE VICINITY OF GFK.

Date: 2003-11 · Aircraft: PA-34-200 Seneca I · Phase: cruise

Anomalies: airspace-violation-all-types|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy

Synopsis

PA34 PLT INADVERTENTLY ENTERS A TFR DURING A CONTRACTED FLT IN THE VICINITY OF GFK.

Narrative

OUR TRAINER NEEDED A NITROGEN CHARGE IN THE NOSEWHEEL STRUT. THIS CAUSED A DELAY IN MY SCHEDULE AND MY LAST TRAINING FLT TERMINATED AT XA50 WITH A PLANNED DEP TIME OF XB00 FOR AN AERIAL SCIENCE MONITOR FLT OF 4 HRS DURATION. I HAD MONITORED WX RPTS AND FORECASTS THROUGHOUT THE DAY AND THE WX PICTURE WAS BENIGN. SINCE SEP/TUE/01; OUR REGIONAL AUTOMATED FSS HAS MADE AVAILABLE A RECORDED LIST OF FDC NOTAMS AFFECTING THE NAS. THIS LIST IS SEQUENTIALLY TAGGED WITH A PHONETIC IDENT EACH TIME IT IS UPDATED. AFTER VERIFYING NOTAM INFO WAS STILL CURRENT (RECORDED ON AUG/FRI/03) VIA THE TELEPHONE INFO BRIEFING SVC; I FELT COMFORTABLE THAT NO NEW TFR'S APPLIED TO MY PLANNED OP. HOWEVER; WHEN I RPTED MY POS TO GRAND FORKS APCH; I WAS INFORMED THAT I HAD PENETRATED A TFR RELATING TO A POLICE OP SURROUNDING A RECENT CIVIL EVENT. I DID NOT SPEAK DIRECTLY TO AN AFSS BRIEFER. INSTEAD I RELIED SOLELY UPON TIBS. AND; I WAS AWARE OF THE INVESTIGATION; BUT IT DID NOT TRIGGER IN MY MIND THE POTENTIAL OF A TFR. THIS TFR WAS NOT MENTIONED IN 2 ATIS BROADCASTS FROM GFK. THE TFR IS BASED UPON THE GRK VORTAC. WHEN RADAR CONTACT WAS ESTABLISHED WITH GFK APCH; MY TARGET WAS IDENTED WITHIN THE TFR. I CLBED IMMEDIATELY AFTER APCH DESCRIBED THE STRUCTURE OF THE TFR. AFTER THE FLT; I INITIATED CONTACT WITH GRK AFSS (THE FAA'S COORDINATOR FOR THIS TFR) TO DISCUSS THE EVENT AND IDENT MYSELF IN ORDER TO FACILITATE WHATEVER REQUIRED PROCESS TO FOLLOW.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.