Pilot of an atx twin inadvertently entered a 'hot MOA' due to tuning his VOR-DME to the wrong frequency for the intersection to which cleared.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	497670
Time
Date	200101
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	navaid : lse.vor
State Reference	WI
Altitude	msl single value : 5000
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zmp.artcc
Operator	common carrier : charter
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Operating Under FAR Part	Part 135
Navigation In Use	other vortac
Flight Phase	climbout : intermediate altitude
Route In Use	departure other enroute airway : v129.airway
Flight Plan	IFR
Person 1
Affiliation	company : air taxi
Function	flight crew : single pilot
Qualification	pilot : multi engine pilot : atp pilot : cfi
Experience	flight time last 90 days : 50 flight time total : 15000 flight time type : 400
ASRS Report	497670
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Events
Anomaly	airspace violation : entry non adherence : far non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued alert controller : provided flight assist flight crew : exited penetrated airspace other
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On an IFR night departure off of lacrosse, wi, I was given runway heading (360 degrees) and a climb to 5000 ft MSL. After takeoff and when contacting ZMP, I was cleared to calms intersection, direct eau claire, direct rhinelander. I looked up calms intersection and put 359 degrees/24 DME in the RNAV and proceeded direct. My mistake was that I misread the chart and left lacrosse VOR (lse) 108.4 in as the frequency, instead of using nodine VOR (odi) 117.9. That caused me to be 10 NM east of calms intersection and 5 NM inside of the falls 1 MOA. ZMP caught the error when they got me on radar. They then turned me to 270 degrees until clear of the MOA. I do not believe there was any conflict with other aircraft. To keep the problem from happening again, I should ask the controling center to define the intersection, ie, off the odi 117.9 359 degree/24 NM. I thought about doing that, but then looked it up myself. It was at night, in the WX, transitioning from takeoff to climb and I selected the wrong frequency.

Original NASA ASRS Text

Title: PLT OF AN ATX TWIN INADVERTENTLY ENTERED A 'HOT MOA' DUE TO TUNING HIS VOR-DME TO THE WRONG FREQ FOR THE INTXN TO WHICH CLRED.

Narrative: ON AN IFR NIGHT DEP OFF OF LACROSSE, WI, I WAS GIVEN RWY HDG (360 DEGS) AND A CLB TO 5000 FT MSL. AFTER TKOF AND WHEN CONTACTING ZMP, I WAS CLRED TO CALMS INTXN, DIRECT EAU CLAIRE, DIRECT RHINELANDER. I LOOKED UP CALMS INTXN AND PUT 359 DEGS/24 DME IN THE RNAV AND PROCEEDED DIRECT. MY MISTAKE WAS THAT I MISREAD THE CHART AND LEFT LACROSSE VOR (LSE) 108.4 IN AS THE FREQ, INSTEAD OF USING NODINE VOR (ODI) 117.9. THAT CAUSED ME TO BE 10 NM E OF CALMS INTXN AND 5 NM INSIDE OF THE FALLS 1 MOA. ZMP CAUGHT THE ERROR WHEN THEY GOT ME ON RADAR. THEY THEN TURNED ME TO 270 DEGS UNTIL CLR OF THE MOA. I DO NOT BELIEVE THERE WAS ANY CONFLICT WITH OTHER ACFT. TO KEEP THE PROB FROM HAPPENING AGAIN, I SHOULD ASK THE CTLING CTR TO DEFINE THE INTXN, IE, OFF THE ODI 117.9 359 DEG/24 NM. I THOUGHT ABOUT DOING THAT, BUT THEN LOOKED IT UP MYSELF. IT WAS AT NIGHT, IN THE WX, TRANSITIONING FROM TKOF TO CLB AND I SELECTED THE WRONG FREQ.

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.