Narrative:

Went up to familiarize myself with new GPS 530 in aircraft. Home based at ezf. I went to fly the GPS runway 24 approach for practice. I believed that by staying over the river, I would remain clear of the ADIZ. I intercepted durwo intersection, performed the procedure turn back to durwo and flew approach to ezf. Got call from ezf to call potomac approach with an ADIZ violation. Have been flying with garmin 296/and now 530. Neither depicts the ADIZ boundary, yet are supposed to be sufficient for flight navigation. Class B is depicted. Other traffic was in the area. Dependence on GPS to provide airspace alert without realizing that the southern boundary ADIZ is not contained on GPS, only the class B boundary.

Google
 

Original NASA ASRS Text

Title: DC ADIZ VIOLATION BY A PA32 PVT PLT WHEN TESTING HIS NEW GPS SYS NEAR INTXN DURWO ON FREQ WITH TWR AT EZF.

Narrative: WENT UP TO FAMILIARIZE MYSELF WITH NEW GPS 530 IN ACFT. HOME BASED AT EZF. I WENT TO FLY THE GPS RWY 24 APCH FOR PRACTICE. I BELIEVED THAT BY STAYING OVER THE RIVER, I WOULD REMAIN CLR OF THE ADIZ. I INTERCEPTED DURWO INTXN, PERFORMED THE PROC TURN BACK TO DURWO AND FLEW APCH TO EZF. GOT CALL FROM EZF TO CALL POTOMAC APCH WITH AN ADIZ VIOLATION. HAVE BEEN FLYING WITH GARMIN 296/AND NOW 530. NEITHER DEPICTS THE ADIZ BOUNDARY, YET ARE SUPPOSED TO BE SUFFICIENT FOR FLT NAV. CLASS B IS DEPICTED. OTHER TFC WAS IN THE AREA. DEPENDENCE ON GPS TO PROVIDE AIRSPACE ALERT WITHOUT REALIZING THAT THE SOUTHERN BOUNDARY ADIZ IS NOT CONTAINED ON GPS, ONLY THE CLASS B BOUNDARY.

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