Date: 201203
Local time of day: 1201-1800
Location: GYY.Airport, IN
Flight conditions: VMC
Weather elements / visibility: 20
Light: Daylight
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class E ZAU
ATC / advisory: Tower GYY
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Sea; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Glider; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Human-Machine Interface; Communication Breakdown; Situational Awareness
Anomaly: Airspace Violation All Types
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Flew through TFR about 1 hour after it became active along Chicago shoreline in an SR22 with its owner/customer. IFR training to GYY; flight plan remarks and ATC informed of intention to fly VFR on to PWK as part of training mission. ATC said nothing about the TFR before or after reaching GYY (Chicago Approach or GYY Tower). After shooting ILS at GYY canceled IFR and continued up lake shore; GYY Tower dumped us without any comment on TFR (and they were not busy). Listened to Approach briefly; but because of speed and training discussions didn't call Approach again and switched to PWK ATIS (which had nothing on the TFR until AFTER our incident - then they added it to the ATIS info). Switched to PWK Tower frequency around downtown area; no one tried to call us. Called PWK at shoreline east of PWK inbound; again; no comments until approach called them after we landed and had us contact them by phone. That was our first information that we'd penetrated an active TFR. No TFR info appeared on the Garmin Perspective System. This info did appear later (the rings on the map) after a number of reboots and another 30 minutes of flying it farther north; a full 3 hours into the TFR period. Nothing was there after over an hour of flying previously on the way to Chicago. This data appeared immediately in ForeFlight and on another SR22 Avidyne system with XM booted up a few minutes after landing at PWK. I am contacting Garmin to see why this info was not displayed on the Perspective system properly - it doesn't make any sense; have not been able to reach tech support yet.Customer and aircraft owner is a licensed and current Private pilot working on instrument rating. I usually call FSS to check NOTAMs and customer's briefing data (almost every day!). The plane ran 4 hours late getting out of shop (not avionics related) and I was interrupted at least three times trying to call FSS. First time in a long time I didn't check via phone. Met customer at his plane and asked him for NOTAM info. He said there wasn't anything pertinent; saw DUATS info on his iPad and nothing there appeared to be pertinent to a training flight in good VMC. Scanned NOTAMS but missed TFRs embedded in FDC section (I thought they would be listed separately; so saw usual list of approach items but missed TFR entry - took 10 minutes to find it after landing at PWK). Didn't get any graphical TFR data via customer briefing data. Unfortunately chose this day to teach VOR/VHF navigation. Left iPad under the seat and didn't put waypoints into GPS; though it showed position and XM weather was otherwise working. But we didn't have ForeFlight up with its depiction of the TFR. We called XM right away. They could not confirm that TFR info was broadcast; but it did show up on other systems (Avidyne MFD in another SR22 and ForeFlight on an iPad).Summary:1) Missed personal voice briefing and trusted customer's DUATS briefing - after previously coaching him on why calling FSS is a better option. Didn't find TFR info buried in huge FDC NOTAM section.2) No display of TFR on Garmin Perspective - and it usually works. Need explanation of this!3) No mention of TFR by Chicago Approach or Gary Tower; etc.4) Didn't pull out iPad with ForeFlight because of training scenario.TFRs should not be part of FDC NOTAMS! They should be shown separately and more easily found. I never thought I'd even come close to busting a TFR - I am very aware of these and the frequency with which they pop up. I get briefings all the time; I use XM to confirm known TFRs and catch any surprises (they are usually displayed at least a day or two in advance). This situation is very frustrating - we really thought we were looking at necessary data to fly safely and appropriately. This was a hard way to learn about DUATS FDC NOTAM's organization for the first time. I am also concerned that ATC knew our intentions and didn't take a few seconds to ask if we knew about the TFR. I know it isn't necessarily theirjob with VFR operations but it sure wouldn't hurt; especially when our communicated intentions clearly could put us in the TFR.

Callback: Calls were made to Garmin and XM to try and determine the cause of the late update of the Perspective System on the SR22. No explanations were forthcoming.



Synopsis: SR22 Instructor reports inadvertently entering a TFR beneath ORD Class B during a VFR flight to PWK. No TFR information appeared on the Garmin Perspective System until after several reboots; after the fact.