# Incident 20070511008359I: Cessna 172K, San Diego, CA, May 11, 2007

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 11, 2007, 16:16 local time
- Place: San Diego, CA
- Damage: No damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Operator: CLWS
- Location: 32.7153° N, 117.1573° W: Placed by OpenAirDocs: center of San Diego, CA, within about 10 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.7153&lon=-117.1573&mi=10
- Aircraft: N84595, registered now (https://openairdocs.org/aircraft/N84595) (OpenAirDocs)
- Registry model: Cessna 172K (registry code 2072430, https://openairdocs.org/model/cessna-172k) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172K
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 80 total, 4 in this make and model, 7 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20070511008359I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) THE PILOT WAS A TEMPORARY VISITOR AND HAD FLOWN ONLY 2 HOURS AS PILOT-IN-COMMAND IN THE UNITED STATES. HE OBTAINED HIS U.S. PRIVATE PILOT CERTIFICATE ON THE BASIS OF HIS UK PPL ON 05/08/07 BY THE SAN FSDO. THE PILOT INADVERTENTLY AND UNKNOWINGLY CROSSED THE ADIZ INTO MEXICO AND THEN BACK INTO U.S. AIRSPACE NEAR OTAY, CA. TWO U.S. MILITARY FIGHTER JETS AND ONE IMMIGRATION/CUSTOMS ENFORCEMENT (ICE) CESSNA-550 JET INTERCEPTED THE PILOT'S AIRCRAFT. THE PILOT ESTABLISHED COMMUNICATIONS WITH THE INTERCEPTING AIRCRAFT AND COMPLIED WITH ALL INSTRUCTIONS, LANDING UNEVENTFULLY AT KMYF. THE PILOT WAS QUESTIONED FOR SEVERAL HOURS BY ICE, FBI, AND TSA OFFICIALS, THEN RELEASED. SEE ATTACHED SHEETS FOR PILOT'S STATEMENT (TELECON) ON 05/16/07 FAA FORM 1360-33.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.