A CFI with a student are informed by us customs that they are in violation of the washington ADIZ. Later, out that they were mistaken for another aircraft.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	599953
Time
Date	200311
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : w50.airport
State Reference	MD
Altitude	msl single value : 1500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pct.tracon
Operator	general aviation : instructional
Make Model Name	Cessna 152
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Route In Use	approach : traffic pattern
Flight Plan	DVR
Person 1
Affiliation	other
Function	instruction : instructor
Qualification	pilot : multi engine pilot : instrument pilot : commercial pilot : cfi
Experience	flight time last 90 days : 80 flight time total : 15000 flight time type : 3000
ASRS Report	599953
Person 2
Affiliation	other
Function	instruction : trainee
Events
Anomaly	airspace violation : entry non adherence : far non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Airspace Structure FAA
Primary Problem	FAA

Narrative:

Filed ADIZ/VFR flight plan for traffic pattern work within ADIZ. Picked up clearance from potomac clearance delivery with instructions: squawk XXXX and remain on advisory frequency (CTAF) in the pattern. (Routine procedure in this area.) received call from united states customs after flight identing aircraft by the n-number and squawk code XXXX with statement we were not in contact with ATC. I explained the normal procedure for takeoffs and lndgs (and also, as clearance was received) was to remain on the CTAF. I was instructed to call potomac TRACON and spoke to a supervisor. The potomac supervisor stated the problem was my aircraft was observed miles south of the airport. I stated we were within less than 1 mi of the airport and under 1500 ft for the whole flight. I was given a pilot deviation and told the radar traces would be reviewed. I was given a phone number to call manager on monday. The call to the manager on monday indicated that the deviation had been assigned to a different aircraft deviation and there was no record of any deviation against me or my aircraft on the time and day in question.

Original NASA ASRS Text

Title: A CFI WITH A STUDENT ARE INFORMED BY US CUSTOMS THAT THEY ARE IN VIOLATION OF THE WASHINGTON ADIZ. LATER, OUT THAT THEY WERE MISTAKEN FOR ANOTHER ACFT.

Narrative: FILED ADIZ/VFR FLT PLAN FOR TFC PATTERN WORK WITHIN ADIZ. PICKED UP CLRNC FROM POTOMAC CLRNC DELIVERY WITH INSTRUCTIONS: SQUAWK XXXX AND REMAIN ON ADVISORY FREQ (CTAF) IN THE PATTERN. (ROUTINE PROC IN THIS AREA.) RECEIVED CALL FROM UNITED STATES CUSTOMS AFTER FLT IDENTING ACFT BY THE N-NUMBER AND SQUAWK CODE XXXX WITH STATEMENT WE WERE NOT IN CONTACT WITH ATC. I EXPLAINED THE NORMAL PROC FOR TKOFS AND LNDGS (AND ALSO, AS CLRNC WAS RECEIVED) WAS TO REMAIN ON THE CTAF. I WAS INSTRUCTED TO CALL POTOMAC TRACON AND SPOKE TO A SUPVR. THE POTOMAC SUPVR STATED THE PROB WAS MY ACFT WAS OBSERVED MILES S OF THE ARPT. I STATED WE WERE WITHIN LESS THAN 1 MI OF THE ARPT AND UNDER 1500 FT FOR THE WHOLE FLT. I WAS GIVEN A PLTDEV AND TOLD THE RADAR TRACES WOULD BE REVIEWED. I WAS GIVEN A PHONE NUMBER TO CALL MGR ON MONDAY. THE CALL TO THE MGR ON MONDAY INDICATED THAT THE DEV HAD BEEN ASSIGNED TO A DIFFERENT ACFT DEV AND THERE WAS NO RECORD OF ANY DEV AGAINST ME OR MY ACFT ON THE TIME AND DAY IN QUESTION.

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.