After 2 altitude crossing restrs missed and 2 MSAW alerts, a high total time ATP citabria pilot makes a visual out of an improperly flown VOR approach to runway 21 at smo, ca.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	620330
Time
Date	200406
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : smo.vor
State Reference	CA
Altitude	msl bound lower : 900 msl bound upper : 2600
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tower : smo.tower
Operator	general aviation : personal
Make Model Name	Champion Citabria
Operating Under FAR Part	Part 91
Navigation In Use	other other vortac
Flight Phase	descent : approach descent : intermediate altitude
Route In Use	approach : instrument non precision
Flight Plan	IFR
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : atp pilot : multi engine
Experience	flight time last 90 days : 20 flight time total : 20000 flight time type : 150
ASRS Report	620330
Person 2
Affiliation	government : faa
Function	controller : local
Events
Anomaly	aircraft equipment problem : critical altitude deviation : excursion from assigned altitude altitude deviation : overshoot inflight encounter : weather non adherence : published procedure other anomaly
Independent Detector	atc equipment : msaw other controllera
Resolutory Action	controller : issued alert flight crew : took precautionary avoidance action flight crew : overrode automation flight crew : became reoriented other
Supplementary
Problem Areas	Flight Crew Human Performance Aircraft
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On VOR 21 approach to smo, using raw data VOR as primary reference. Have garmin 300 and 196 on board for situational awareness. Mistakenly interpreted 'beuey' location on #1 GPS and compared to another. Distraction caused possible altitude bust at bevey. Corrected as controller called to my attention. (I also realized at that time my altimeter had stuck. I have since had it replaced.) as I confirmed bevey, I continued down to culve. Again, controller called 'altitude alert' at culve. I confirmed altimeter setting and tapped my altimeter. By culve, I had visual contact and continued for an uneventful landing. I believe a faulty altimeter and too much 'glass' in my little citabria was a problem. I hadn't really managed it too well on the approach. I became distraction comparing 2 very different pictures. I will probably use only 1 GPS and 1 VOR on that approach next time. I think I have realized too much 'glass,' not managed properly, can be a problem.

Original NASA ASRS Text

Title: AFTER 2 ALT XING RESTRS MISSED AND 2 MSAW ALERTS, A HIGH TOTAL TIME ATP CITABRIA PLT MAKES A VISUAL OUT OF AN IMPROPERLY FLOWN VOR APCH TO RWY 21 AT SMO, CA.

Narrative: ON VOR 21 APCH TO SMO, USING RAW DATA VOR AS PRIMARY REF. HAVE GARMIN 300 AND 196 ON BOARD FOR SITUATIONAL AWARENESS. MISTAKENLY INTERPED 'BEUEY' LOCATION ON #1 GPS AND COMPARED TO ANOTHER. DISTR CAUSED POSSIBLE ALT BUST AT BEVEY. CORRECTED AS CTLR CALLED TO MY ATTN. (I ALSO REALIZED AT THAT TIME MY ALTIMETER HAD STUCK. I HAVE SINCE HAD IT REPLACED.) AS I CONFIRMED BEVEY, I CONTINUED DOWN TO CULVE. AGAIN, CTLR CALLED 'ALT ALERT' AT CULVE. I CONFIRMED ALTIMETER SETTING AND TAPPED MY ALTIMETER. BY CULVE, I HAD VISUAL CONTACT AND CONTINUED FOR AN UNEVENTFUL LNDG. I BELIEVE A FAULTY ALTIMETER AND TOO MUCH 'GLASS' IN MY LITTLE CITABRIA WAS A PROB. I HADN'T REALLY MANAGED IT TOO WELL ON THE APCH. I BECAME DISTR COMPARING 2 VERY DIFFERENT PICTURES. I WILL PROBABLY USE ONLY 1 GPS AND 1 VOR ON THAT APCH NEXT TIME. I THINK I HAVE REALIZED TOO MUCH 'GLASS,' NOT MANAGED PROPERLY, CAN BE A PROB.

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.