A B737-200 does not cross jokur intersection at the required altitude.

Attributes
ACN	416280
Time
Date	199810
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : dag
State Reference	CA
Altitude	msl bound lower : 24000 msl bound upper : 25000
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Controlling Facilities	artcc : zla
Operator	common carrier : air carrier
Make Model Name	B737-200
Operating Under FAR Part	Part 121
Navigation In Use	other vortac
Flight Phase	cruise other descent other
Route In Use	arrival other arrival star : star enroute airway : zla
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain observation : company check pilot oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 12000 flight time type : 10000
ASRS Report	416280
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	aircraft equipment problem : less severe altitude deviation : undershoot altitude deviation : crossing restriction not met non adherence : published procedure non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	Other
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation

Narrative:

The event, during flight from lax to las on B737-200A using VOR navigation. After passing dag VOR at FL250, cleared to cross jokur intersection at FL240. Navigating off the #1 VOR, it failed prior to jokur and during subsequent xchk with the #2 failed to reach FL240 at jokur until approximately 5 mi beyond. Also, the routing was in question because bld VOR was OTS. I queried the controller, was then given new heading and altitude instructions. No conflicts occurred. ATC was saturated with calls. I was flying with a new first officer, unfamiliar with the particular model of aircraft and with the route. During the problem solving plus trying to fly, instruct the new first officer and comply with the arrival, there was also interruption to the flight deck from the cabin attendant. The flight is a scheduled 47 min event. I believe that better communication from ATC, more concentrated conception on the flying without undue distraction and preparation from all parties, even with the equipment failure, will result in an uneventful event.

Original NASA ASRS Text

Title: A B737-200 DOES NOT CROSS JOKUR INTXN AT THE REQUIRED ALT.

Narrative: THE EVENT, DURING FLT FROM LAX TO LAS ON B737-200A USING VOR NAV. AFTER PASSING DAG VOR AT FL250, CLRED TO CROSS JOKUR INTXN AT FL240. NAVING OFF THE #1 VOR, IT FAILED PRIOR TO JOKUR AND DURING SUBSEQUENT XCHK WITH THE #2 FAILED TO REACH FL240 AT JOKUR UNTIL APPROX 5 MI BEYOND. ALSO, THE ROUTING WAS IN QUESTION BECAUSE BLD VOR WAS OTS. I QUERIED THE CTLR, WAS THEN GIVEN NEW HDG AND ALT INSTRUCTIONS. NO CONFLICTS OCCURRED. ATC WAS SATURATED WITH CALLS. I WAS FLYING WITH A NEW FO, UNFAMILIAR WITH THE PARTICULAR MODEL OF ACFT AND WITH THE RTE. DURING THE PROB SOLVING PLUS TRYING TO FLY, INSTRUCT THE NEW FO AND COMPLY WITH THE ARR, THERE WAS ALSO INTERRUPTION TO THE FLT DECK FROM THE CABIN ATTENDANT. THE FLT IS A SCHEDULED 47 MIN EVENT. I BELIEVE THAT BETTER COM FROM ATC, MORE CONCENTRATED CONCEPTION ON THE FLYING WITHOUT UNDUE DISTR AND PREPARATION FROM ALL PARTIES, EVEN WITH THE EQUIP FAILURE, WILL RESULT IN AN UNEVENTFUL EVENT.

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.