CL65 crew had an altitude overshoot within cleared the visual approach to runway 18L, at night, at m...

Attributes
ACN	624178
Time
Date	200406
Day	Wed
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : mco.airport
State Reference	FL
Altitude	msl bound lower : 2100 msl bound upper : 2500
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : mco.tracon
Operator	common carrier : air carrier
Make Model Name	Regional Jet CL65, Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : vacating altitude descent : approach
Route In Use	approach : visual arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 500 flight time total : 23000 flight time type : 1600
ASRS Report	624178
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	altitude deviation : crossing restriction not met altitude deviation : overshoot non adherence : published procedure non adherence : far non adherence : company policies non adherence : clearance
Independent Detector	other flight crewb
Resolutory Action	flight crew : became reoriented
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On approach to mco, we were being radar vectored to runway 18L (no ILS approach available for this runway). We were in 'white data' using the FMS 'visual mode' to assist in the visual approach to the runway. We were high and at a right angle to the approach. We requested a left 270 degree turn to lose altitude and realign with the final approach corridor. As we came out of the turn, I saw a beacon light in the distance and became confused as to whether it was executive airport or the international airport that I was seeing. The VOR is located on the executive airport, but was not showing on my moving map. We were instructed to cross the VOR at 2500 ft and cleared for the visual approach. Not seeing the VOR displaced, I started my descend assuming that I had passed it. My first officer noted that we had not passed it and the crossing restr. I stopped the descent and passed over the VOR at 2100 ft. I then noted that the VOR symbol had been obscured by the white line that marked the final approach course for us on the moving map display. We intercepted VASI GS and made a normal landing without further incident.

Original NASA ASRS Text

Title: CL65 CREW HAD AN ALT OVERSHOOT WITHIN CLRED THE VISUAL APCH TO RWY 18L, AT NIGHT, AT MCO.

Narrative: ON APCH TO MCO, WE WERE BEING RADAR VECTORED TO RWY 18L (NO ILS APCH AVAILABLE FOR THIS RWY). WE WERE IN 'WHITE DATA' USING THE FMS 'VISUAL MODE' TO ASSIST IN THE VISUAL APCH TO THE RWY. WE WERE HIGH AND AT A R ANGLE TO THE APCH. WE REQUESTED A L 270 DEG TURN TO LOSE ALT AND REALIGN WITH THE FINAL APCH CORRIDOR. AS WE CAME OUT OF THE TURN, I SAW A BEACON LIGHT IN THE DISTANCE AND BECAME CONFUSED AS TO WHETHER IT WAS EXECUTIVE ARPT OR THE INTL ARPT THAT I WAS SEEING. THE VOR IS LOCATED ON THE EXECUTIVE ARPT, BUT WAS NOT SHOWING ON MY MOVING MAP. WE WERE INSTRUCTED TO CROSS THE VOR AT 2500 FT AND CLRED FOR THE VISUAL APCH. NOT SEEING THE VOR DISPLACED, I STARTED MY DSND ASSUMING THAT I HAD PASSED IT. MY FO NOTED THAT WE HAD NOT PASSED IT AND THE XING RESTR. I STOPPED THE DSCNT AND PASSED OVER THE VOR AT 2100 FT. I THEN NOTED THAT THE VOR SYMBOL HAD BEEN OBSCURED BY THE WHITE LINE THAT MARKED THE FINAL APCH COURSE FOR US ON THE MOVING MAP DISPLAY. WE INTERCEPTED VASI GS AND MADE A NORMAL LNDG WITHOUT FURTHER INCIDENT.

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.

CL65 crew had an altitude overshoot within cleared the visual approach to runway 18L, at night, at mco.