Cessna pilot reports inadvertently entering a tfr after requesting the NOTAM on his iphone; but not ...

Narrative:

I reviewed the tfr below before departing to apc on a VFR night flight. I made the mistake of incorrectly reading the tfr on my iphone as I read the first section regarding the 30 NM radius from the sfo VOR. When I got to the end of the lines referring to the 30 NM off sfo there was a blank section of 4 empty lines so I did not realize there was more to the tfr regarding the sau VOR. I saw that I was 40 NM from sfo and apc was 36NM from sfo. I then felt I would be clear of the tfr so I made the direct flight. Before departing I was able to pick up ASOS while taxing on the ground. ASOS informed me the tower was closed; the weather conditions were VFR; that there was a tfr in the bay area; no mention of napa being within the tfr. I know it is my responsibility to know before I go; however had I heard that napa was within the tfr it could have been helpful and I would have called center on the ground and requested to make the flight. I learned a hard lesson here as I should have contacting center and requested a code because I was planning a flight so close to the tfr. As an instructor I teach my students to be in communications with ATC whenever possible and I have over 300 hours last year on IFR flights so I am very comfortable with the ATC system. I take this issue very seriously and will share with others my mistake.FAA to establish tfr over san francisco; ca ==> 30 NM radius tfr <==location: san francisco VOR/DME(sfo) surface to 17;999-ft-MSL(I did not read past this point because it looked as if this was the end of the message on my iphone.)==> 10 NM radius no-fly zone <==location: san francisco VOR/DME (sfo) surface to 17;999-ft-MSL ==> 30 NM radius tfr <==location: on the sausalito VORTAC (sau) 113 degree radial at 5.9 nautical miles surface to 17;999-ft-MSL ==> 10 NM radius no-fly zone <==location: on the sausalito VORTAC (sau) 113 degree radial at 5.9 nautical miles surface to 17;999-ft-MSL ==> affected public use airports <==ksfo san francisco intl ksql san carlos khaf half moon bay koak metropolitan oakland intl khwd hayward executive kpao palo alto arpt of santa clara co ksjc norman Y. Mineta san jose intl klvk livermore muni kccr buchanan field kdvo gnoss field 0q3 sonoma valley kapc napa county 0q9 sonoma skypark O69 petaluma muni view the new NOTAM page.

Original NASA ASRS Text

Title: Cessna pilot reports inadvertently entering a TFR after requesting the NOTAM on his iPhone; but not seeing the complete description due to gaps in the text message.

Narrative: I reviewed the TFR below before departing to APC on a VFR night flight. I made the mistake of incorrectly reading the TFR on my iPhone as I read the first section regarding the 30 NM radius from the SFO VOR. When I got to the end of the lines referring to the 30 NM off SFO there was a blank section of 4 empty lines so I did not realize there was more to the TFR regarding the SAU VOR. I saw that I was 40 NM from SFO and APC was 36NM from SFO. I then felt I would be clear of the TFR so I made the direct flight. Before departing I was able to pick up ASOS while taxing on the ground. ASOS informed me the Tower was closed; the weather conditions were VFR; that there was a TFR in the Bay Area; no mention of Napa being within the TFR. I know it is my responsibility to know before I go; however had I heard that Napa was within the TFR it could have been helpful and I would have called Center on the ground and requested to make the flight. I learned a hard lesson here as I should have contacting Center and requested a code because I was planning a flight so close to the TFR. As an instructor I teach my students to be in communications with ATC whenever possible and I have over 300 hours last year on IFR flights so I am very comfortable with the ATC system. I take this issue very seriously and will share with others my mistake.FAA TO ESTABLISH TFR OVER SAN FRANCISCO; CA ==> 30 NM RADIUS TFR <==Location: SAN FRANCISCO VOR/DME(SFO) Surface to 17;999-FT-MSL(I did not read past this point because it looked as if this was the end of the message on my iPhone.)==> 10 NM RADIUS NO-FLY ZONE <==Location: SAN FRANCISCO VOR/DME (SFO) Surface to 17;999-FT-MSL ==> 30 NM RADIUS TFR <==Location: On the SAUSALITO VORTAC (SAU) 113 degree radial at 5.9 nautical miles Surface to 17;999-FT-MSL ==> 10 NM RADIUS NO-FLY ZONE <==Location: On the SAUSALITO VORTAC (SAU) 113 degree radial at 5.9 nautical miles Surface to 17;999-FT-MSL ==> AFFECTED PUBLIC USE AIRPORTS <==KSFO San Francisco Intl KSQL San Carlos KHAF Half Moon Bay KOAK Metropolitan Oakland Intl KHWD Hayward Executive KPAO Palo Alto Arpt of Santa Clara Co KSJC Norman Y. Mineta San Jose Intl KLVK Livermore Muni KCCR Buchanan Field KDVO Gnoss Field 0Q3 Sonoma Valley KAPC Napa County 0Q9 Sonoma Skypark O69 Petaluma Muni View the new NOTAM page.

Data retrieved from NASA's ASRS site as of July 2013 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.

Attributes
ACN	995466
Time
Date	201202
Local Time Of Day	1801-2400
Place
Locale Reference	APC.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	Cessna Single Piston Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Route In Use	Direct
Flight Plan	None
Component
Aircraft Component	Tablet
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Multiengine Flight Crew Flight Instructor Flight Crew Instrument
Experience	Flight Crew Last 90 Days 94 Flight Crew Total 3458 Flight Crew Type 12
Events
Anomaly	Airspace Violation All Types

Cessna pilot reports inadvertently entering a tfr after requesting the NOTAM on his iphone; but not seeing the complete description due to gaps in the text message.