37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 914478 |
Time | |
Date | 201010 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | PCT.TRACON |
State Reference | VA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | Visual Approach |
Flight Plan | None |
Component | |
Aircraft Component | Electronic Flt Bag (EFB) |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Private Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 65 Flight Crew Total 2700 Flight Crew Type 800 |
Events | |
Anomaly | Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
VFR flight from [on a] clear and sunny day; [I] contacted FSS for a briefing. Logged into aviation website to plan trip; check for NOTAMS; weather; and laid out flight plan. Departed [but] I realized that I did not put a waypoint in to go around the R-6611A and R-6613A zone. I just started using the ipad for my charts (icharts; flight prep); I had the updated version of the baltimore/washington terminal chart up. As I made the turn from 2w6 waypoint I realized I did not have a waypoint in to go around the restricted 6611A and 6613A zone. I had the ipad terminal map zoomed in to look at the 6611A zone and saw the sfra ring but with it zoomed in; I thought I was looking at the speed restriction zone. At that point I deviated to the north to avoid the R-6611A zone not realizing that I was flying into the sfra. I went just north of that zone and once clear I navigated direct to my destination. I did not realize that I had flown into the sfra until I landed. The FBO told me to contact potomac TRACON. I spoke with TRACON and was informed me that I clipped the zone; 30 miles on the 166 degree bearing. Other relevant information. I have another airplane that I usually fly; this aircraft has been for sale for the past two years. I did not update the moving map or GPS since I was not flying it much. The moving map shows the old washington ATIS zone which further confused the situation. I knew it was the old zone and that is why I was looking at the baltimore/washington terminal map on the ipad. Earlier in the month; I went to the FAA safety site to get my certificate for the sfra course. I could not get into the site due to a glitch with the password. I called the FAA and they did get back to me later that day. I did review the course material but did not finish. I need to finish the course for the sfra. I need to update the GPS and moving map that would have made my situational awareness very clear. I need to be careful when using the new ipad format in the zoom and should have the paper maps for back up to see more of the area and not just a limited area that is shown on the ipad. I need to know the flight plan better especially around the sfra. I got comfortable with my abilities and past flights around the eastern side of the sfra and with my first time flight to this airport; I should have studied the map and what I should be aware of.
Original NASA ASRS Text
Title: A pilot reported entering the PCT SFRA as he was attempting to avoid a warning area but did not have either his GPS or area charts to track his location and stay clear of the SFRA.
Narrative: VFR flight from [on a] clear and sunny day; [I] contacted FSS for a briefing. Logged into aviation website to plan trip; check for NOTAMS; weather; and laid out flight plan. Departed [but] I realized that I did not put a waypoint in to go around the R-6611A and R-6613A zone. I just started using the iPad for my charts (iCharts; flight prep); I had the updated version of the Baltimore/Washington Terminal Chart up. As I made the turn from 2w6 waypoint I realized I did not have a waypoint in to go around the restricted 6611A and 6613A zone. I had the iPad terminal map zoomed in to look at the 6611A zone and saw the SFRA ring but with it zoomed in; I thought I was looking at the speed restriction zone. At that point I deviated to the north to avoid the R-6611A zone not realizing that I was flying into the SFRA. I went just north of that zone and once clear I navigated direct to my destination. I did not realize that I had flown into the SFRA until I landed. The FBO told me to contact Potomac TRACON. I spoke with TRACON and was informed me that I clipped the zone; 30 miles on the 166 degree bearing. Other relevant information. I have another airplane that I usually fly; this aircraft has been for sale for the past two years. I did not update the moving map or GPS since I was not flying it much. The moving map shows the old Washington ATIS zone which further confused the situation. I knew it was the old zone and that is why I was looking at the Baltimore/Washington terminal map on the iPad. Earlier in the month; I went to the FAA Safety site to get my certificate for the SFRA course. I could not get into the site due to a glitch with the password. I called the FAA and they did get back to me later that day. I did review the course material but did not finish. I need to finish the course for the SFRA. I need to update the GPS and moving map that would have made my situational awareness very clear. I need to be careful when using the new iPad format in the zoom and should have the paper maps for back up to see more of the area and not just a limited area that is shown on the IPad. I need to know the flight plan better especially around the SFRA. I got comfortable with my abilities and past flights around the eastern side of the SFRA and with my first time flight to this airport; I should have studied the map and what I should be aware of.
Data retrieved from NASA's ASRS site as of April 2012 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.