Air carrier delays descent because of reported traffic too long and is unable to make crossing restr...

Attributes
ACN	450540
Time
Date	199909
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : sjc.airport
State Reference	CA
Altitude	msl bound lower : 5000 msl bound upper : 5600
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : o90.tracon tower : zzz.tower
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 30l other vortac
Flight Phase	descent : approach descent : intermediate altitude
Route In Use	approach : instrument precision
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : cfi pilot : atp
Experience	flight time last 90 days : 220 flight time total : 16500 flight time type : 4400
ASRS Report	450540
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Events
Anomaly	altitude deviation : crossing restriction not met altitude deviation : overshoot non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Level at 8000 ft we were tracking the localizer runway 30L sjc. Approximately 24 mi southeast of the airport. Traffic was pointed out to us at 10-11 O'clock position as we were cleared to cross klide at 5000 ft. Traffic was spotted on TCASII, 2200 ft below us at 11 O'clock position. Because the traffic was a concern, the descent to cross klide was at 500 FPM until we were clear of the traffic. We never saw the traffic nor did we receive a TA on the TCASII. However, based on TCASII information the crossing at klide was at 5600 ft. The controller said nothing and only after returning to my home did I consider this an issue. I should have informed the controller that we were going to be higher at klide because of the traffic.

Original NASA ASRS Text

Title: ACR DELAYS DSCNT BECAUSE OF RPTED TFC TOO LONG AND IS UNABLE TO MAKE XING RESTR.

Narrative: LEVEL AT 8000 FT WE WERE TRACKING THE LOC RWY 30L SJC. APPROX 24 MI SE OF THE ARPT. TFC WAS POINTED OUT TO US AT 10-11 O'CLOCK POS AS WE WERE CLRED TO CROSS KLIDE AT 5000 FT. TFC WAS SPOTTED ON TCASII, 2200 FT BELOW US AT 11 O'CLOCK POS. BECAUSE THE TFC WAS A CONCERN, THE DSCNT TO CROSS KLIDE WAS AT 500 FPM UNTIL WE WERE CLR OF THE TFC. WE NEVER SAW THE TFC NOR DID WE RECEIVE A TA ON THE TCASII. HOWEVER, BASED ON TCASII INFO THE XING AT KLIDE WAS AT 5600 FT. THE CTLR SAID NOTHING AND ONLY AFTER RETURNING TO MY HOME DID I CONSIDER THIS AN ISSUE. I SHOULD HAVE INFORMED THE CTLR THAT WE WERE GOING TO BE HIGHER AT KLIDE BECAUSE OF THE TFC.

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.