A climbing B737-200 overshot its assigned crossing altitude at arnee on the PRD05 pt pdz departure procedure when given 14000 ft. The sli VOR was OTS.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	427620
Time
Date	199902
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : pdz airport : ont
State Reference	CA
Altitude	msl bound lower : 11000 msl bound upper : 14000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-200
Navigation In Use	other vortac
Route In Use	departure other departure sid : sid enroute airway : lax
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : cfi
Experience	flight time last 90 days : 200 flight time total : 7000 flight time type : 3500
ASRS Report	427620
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	altitude deviation : overshoot altitude deviation : crossing restriction not met conflict : airborne less severe non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Miss Distance	horizontal : 27000 vertical : 1000
Supplementary
Air Traffic Incident	Pilot Deviation

Narrative:

Sli VOR notamed OTS. Assigned prado five departure from ont. Initial climb was to 3000 ft for cessna traffic. Upon clear we were given 'climb unrestr to 7000 ft.' next: 'climb to 14000 ft.' in the climb, we requested a vector for the trm transition since sli VOR was inoperative. Then came a frequency change, and upon check-in the new controller's response was '14000 ft?' I repeated the clearance, and he never questioned us again. Anytime a controller questions your clearance it's scary, but I would not have written except for 2 sidelights. 1) we saw crossing traffic on the nose crossing left to right about 4-5 mi and close to our altitude, with a brief appearance on the TCASII vsi screen (no 'traffic' aural warning). He was far enough away so we never thought a thing about it until our clearance was questioned. 2) there is an 'at or below 11000 ft' restr at 7 DME which would not apply once cleared to 14000 ft with no restrs stated. Again, maybe we were ok, maybe everything worked just like it should, but I thought I'd better write.

Original NASA ASRS Text

Title: A CLBING B737-200 OVERSHOT ITS ASSIGNED XING ALT AT ARNEE ON THE PRD05 PT PDZ DEP PROC WHEN GIVEN 14000 FT. THE SLI VOR WAS OTS.

Narrative: SLI VOR NOTAMED OTS. ASSIGNED PRADO FIVE DEP FROM ONT. INITIAL CLB WAS TO 3000 FT FOR CESSNA TFC. UPON CLR WE WERE GIVEN 'CLB UNRESTR TO 7000 FT.' NEXT: 'CLB TO 14000 FT.' IN THE CLB, WE REQUESTED A VECTOR FOR THE TRM TRANSITION SINCE SLI VOR WAS INOP. THEN CAME A FREQ CHANGE, AND UPON CHK-IN THE NEW CTLR'S RESPONSE WAS '14000 FT?' I REPEATED THE CLRNC, AND HE NEVER QUESTIONED US AGAIN. ANYTIME A CTLR QUESTIONS YOUR CLRNC IT'S SCARY, BUT I WOULD NOT HAVE WRITTEN EXCEPT FOR 2 SIDELIGHTS. 1) WE SAW XING TFC ON THE NOSE XING L TO R ABOUT 4-5 MI AND CLOSE TO OUR ALT, WITH A BRIEF APPEARANCE ON THE TCASII VSI SCREEN (NO 'TFC' AURAL WARNING). HE WAS FAR ENOUGH AWAY SO WE NEVER THOUGHT A THING ABOUT IT UNTIL OUR CLRNC WAS QUESTIONED. 2) THERE IS AN 'AT OR BELOW 11000 FT' RESTR AT 7 DME WHICH WOULD NOT APPLY ONCE CLRED TO 14000 FT WITH NO RESTRS STATED. AGAIN, MAYBE WE WERE OK, MAYBE EVERYTHING WORKED JUST LIKE IT SHOULD, BUT I THOUGHT I'D BETTER WRITE.

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.