37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 518655 |
Time | |
Date | 200107 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : mmtj.airport |
State Reference | FO |
Altitude | agl single value : 0 |
Environment | |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : sct.tracon |
Operator | common carrier : air taxi |
Make Model Name | MU-2 Undifferentiated or Other Model |
Operating Under FAR Part | Part 135 |
Navigation In Use | other vortac |
Flight Phase | landing : roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : single pilot |
Qualification | pilot : atp |
Experience | flight time last 90 days : 120 flight time total : 7790 flight time type : 45 |
ASRS Report | 518655 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | airspace violation : entry incursion : landing without clearance incursion : runway non adherence : far other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Problem Areas | Navigational Facility Flight Crew Human Performance Environmental Factor Airspace Structure ATC Facility |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Approaching sdm at night from pgy VOR, spotted rotating beacon and runway. Canceled IFR, entered traffic pattern and landed. Unfortunately it was mmtj (mexico) 1.7 NM south of sdm. Factors: 1) I was unfamiliar with the area. 2) I expected to see an airport in front of me, and did. 3) runway alignment was similar. Mmtw runway 9/27 -- sdm runway 8/26. Sdm and mmtj are on same approximately radial from pgy. 4) sdm lights are pilot controled lighting and may not have been on when I overflew. (Had the lights in sight, so wasn't concerned about activating them.) 5) no information on approach charts reference another airport so close to sdm. Corrective actions: pilot -- brief unfamiliar areas with VFR charts as well as IFR. Pay attention to detail! (DME -- pgy, runway heading, airport layout). Stay with approach control until landing assured. Government: put note or warning on IFR charts when runway identify may be difficult (or airport identify).
Original NASA ASRS Text
Title: AN MU2B CARGO FLT LANDS AT THE WRONG ARPT WHEN APCHING SDM FROM THE N AT NIGHT AND LANDS WITHOUT CLRNC AT MMTJ, FO.
Narrative: APCHING SDM AT NIGHT FROM PGY VOR, SPOTTED ROTATING BEACON AND RWY. CANCELED IFR, ENTERED TFC PATTERN AND LANDED. UNFORTUNATELY IT WAS MMTJ (MEXICO) 1.7 NM S OF SDM. FACTORS: 1) I WAS UNFAMILIAR WITH THE AREA. 2) I EXPECTED TO SEE AN ARPT IN FRONT OF ME, AND DID. 3) RWY ALIGNMENT WAS SIMILAR. MMTW RWY 9/27 -- SDM RWY 8/26. SDM AND MMTJ ARE ON SAME APPROX RADIAL FROM PGY. 4) SDM LIGHTS ARE PLT CTLED LIGHTING AND MAY NOT HAVE BEEN ON WHEN I OVERFLEW. (HAD THE LIGHTS IN SIGHT, SO WASN'T CONCERNED ABOUT ACTIVATING THEM.) 5) NO INFO ON APCH CHARTS REF ANOTHER ARPT SO CLOSE TO SDM. CORRECTIVE ACTIONS: PLT -- BRIEF UNFAMILIAR AREAS WITH VFR CHARTS AS WELL AS IFR. PAY ATTN TO DETAIL! (DME -- PGY, RWY HDG, ARPT LAYOUT). STAY WITH APCH CTL UNTIL LNDG ASSURED. GOV: PUT NOTE OR WARNING ON IFR CHARTS WHEN RWY IDENT MAY BE DIFFICULT (OR ARPT IDENT).
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.