B737-300 flight crew on approach to bur failed to follow the charted visual approach procedures.

Attributes
ACN	693389
Time
Date	200604
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : whp.airport
State Reference	CA
Altitude	msl bound lower : 2200 msl bound upper : 2500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : bur.tower
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	approach : charted visual
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 240 flight time total : 2000 flight time type : 3500
ASRS Report	693389
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	airspace violation : entry altitude deviation : excursion from assigned altitude conflict : airborne less severe non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	aircraft equipment : tcas other flight crewa
Resolutory Action	controller : issued advisory flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 500 vertical : 500
Supplementary
Problem Areas	Chart Or Publication Flight Crew Human Performance Airspace Structure
Primary Problem	Flight Crew Human Performance

Narrative:

On approach into bur we were cleared for visual approach to runway 15. We were at 5000 ft in the vicinity of OAT mountain. The captain briefed he would follow the profile on four stacks visual approach (ie; 5000 ft until passing OAT mountain; then 3000 ft until final). As we descended to 3000 ft inside san gabriel mountains; he started a dogleg base to final. I said; 'whiteman airport is right there. Do you see it?' he said he saw it. About that time he turned off the autoplt and began asking for confign for landing. Next I noticed we were 2200-2500 ft MSL still angled over whiteman. I said we need to maintain 3000 ft or we'll be in their airspace. About that time we received an RA to monitor vertical speed. He acknowledged and complied with RA. We then received a TA. I called out traffic and saw we were still descending. I reiterated we were too close to whiteman. He acknowledged and leveled off. At this time; tower told us for future reference they needed us to fly an extended centerline final and not a dogleg. The captain called tower once on the ground. They insured the captain there was no further problem; but to make sure to follow the charted final.

Original NASA ASRS Text

Title: B737-300 FLT CREW ON APCH TO BUR FAILED TO FOLLOW THE CHARTED VISUAL APCH PROCS.

Narrative: ON APCH INTO BUR WE WERE CLRED FOR VISUAL APCH TO RWY 15. WE WERE AT 5000 FT IN THE VICINITY OF OAT MOUNTAIN. THE CAPT BRIEFED HE WOULD FOLLOW THE PROFILE ON FOUR STACKS VISUAL APCH (IE; 5000 FT UNTIL PASSING OAT MOUNTAIN; THEN 3000 FT UNTIL FINAL). AS WE DSNDED TO 3000 FT INSIDE SAN GABRIEL MOUNTAINS; HE STARTED A DOGLEG BASE TO FINAL. I SAID; 'WHITEMAN ARPT IS RIGHT THERE. DO YOU SEE IT?' HE SAID HE SAW IT. ABOUT THAT TIME HE TURNED OFF THE AUTOPLT AND BEGAN ASKING FOR CONFIGN FOR LNDG. NEXT I NOTICED WE WERE 2200-2500 FT MSL STILL ANGLED OVER WHITEMAN. I SAID WE NEED TO MAINTAIN 3000 FT OR WE'LL BE IN THEIR AIRSPACE. ABOUT THAT TIME WE RECEIVED AN RA TO MONITOR VERT SPD. HE ACKNOWLEDGED AND COMPLIED WITH RA. WE THEN RECEIVED A TA. I CALLED OUT TFC AND SAW WE WERE STILL DSNDING. I REITERATED WE WERE TOO CLOSE TO WHITEMAN. HE ACKNOWLEDGED AND LEVELED OFF. AT THIS TIME; TWR TOLD US FOR FUTURE REF THEY NEEDED US TO FLY AN EXTENDED CTRLINE FINAL AND NOT A DOGLEG. THE CAPT CALLED TWR ONCE ON THE GND. THEY INSURED THE CAPT THERE WAS NO FURTHER PROB; BUT TO MAKE SURE TO FOLLOW THE CHARTED FINAL.

Data retrieved from NASA's ASRS site as of January 2009 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.