Date: 201606
Local time of day: 1201-1800
Location: BWI.Airport, MD
Flight conditions: VMC
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operating under: Part 91
Flight plan: VFR
Flight phase: Cruise
Airspace: Class B BWI
ATC / advisory: TRACON PCT; Tower BWI
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: Our route is supposed to end at Baltimore Inner Harbor; close to downtown Baltimore. The issue was the status of the TFR for the Baltimore Orioles game. When I called FSS (Lockheed) for the briefing at the start of the day; I specifically asked if the Orioles game had a TFR. All he was able to tell me was that there is a general security/defense NOTAM for stadiums; 1 hour before to 1 hour after games. But he said that he couldn't tell me any specifics about the one in Baltimore. He said there were too many (across the country) to keep track of; plus some games go longer; are rain-delayed; etc.So; on our way back up to Baltimore; I asked Potomac Approach about the status of the TFR; and asked for 3;500 feet over Baltimore to keep clear of it. The controller replied that 'that TFR is expired; stay at or below 1;500 feet through Baltimore. I thought that was strange; it seemed too early for the game to be over. So I asked my crew to check the Internet and find the status of the game. Sure enough; it was still in the top of the 7th inning. Strange.So we continued to Baltimore and Potomac switched us to Baltimore Tower as we got closer. About 10 miles from the TFR I again asked the controller about the TFR and whether we could transit over top at 3;500 feet. At first Tower wasn't sure of the TFR; and then said it went up to 10;000 feet. This was unexpected; because my Foreflight said it only extends to 3;000 feet. Then the controller seemed unsure and said he'd 'check on it.'We were close enough to the edge of the TFR and still hasn't been granted permission to climb to 3;500; so I told Tower that we would divert to the north around the TFR at current altitude (about 1;200 feet). No further issues; we avoided the TFR and proceeded back [on course].The issue here is one of information availability. Why can't FSS advise of these TFRs? I always thought they could (and would); but apparently not. Failing that; how is it that controllers at Potomac Approach and Baltimore Tower do not really know about the TFR; when it starts/ends; the altitude it goes up to; and even whether or not it's in effect? If I didn't have Foreflight (and the background knowledge to check the baseball schedule before I went flying); I wouldn't really have known about this TFR. More seriously; the initial info from Potomac Approach was that the TFR was expired! I was under no obligation to ask for another time; but I did because something didn't feel right. And; even then; additional two controllers got it wrong or weren't really sure of the situation.Not sure how FAA/DOD expects pilots to know about these; when all the official channels don't know about them or can't talk to them. Thankfully; Foreflight seems to be on top of things; but if it weren't for that; I probably would have flown through an active TFR today.




Synopsis: C182 pilot reported being aware of a potential baseball game TFR before departure; but could not get any specific information from the FSS. Enroute information was requested from PCT and BAL Tower about the TFR without receiving any conclusive answer.