Corp mdt does not make altitude crossing restriction.

Attributes
ACN	178296
Time
Date	199105
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : stw airport : teb
State Reference	PA
Altitude	msl bound lower : 6000 msl bound upper : 7000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	Medium Transport, Low Wing, 2 Turbojet Eng
Flight Phase	descent other
Route In Use	arrival star : star enroute airway : n90
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 60 flight time total : 8800 flight time type : 60
ASRS Report	178296
Person 2
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	altitude deviation : undershoot altitude deviation : crossing restriction not met non adherence : far non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

The captain was given a crossing restriction at mugzy intersection of 6000'. As we approached form the northwest out of 20000', he put out air brakes and reduced power adequately to make the restriction. As we passed through 10000', he retracted the air brakes and continued to descend at about 230 KTS indicated. I reiterated the crossing restriction and our distance to go when we were 10 mi out and then 5 mi out. He was no longer aggressively going after the restriction. We crossed mugzy at 7000' in a descent to 6000'. In the past, when I have flown with this captain, he has been lackadaisical about making these restrictions. He is capable of doing the job, but evidently he does not attach any importance to the restrictions. ATC never said a word. It was I'm sure a LOA entry into the next sector's airspace with no traffic conflict. But we are going to kill people some day because of a slack attitude on the part of pilots encouraged by ATC. Do these restrictions exist to separate real traffic, or to ease the ATC workload? Have I missed a write-up on this in your newsletter?

Original NASA ASRS Text

Title: CORP MDT DOES NOT MAKE ALT CROSSING RESTRICTION.

Narrative: THE CAPT WAS GIVEN A XING RESTRICTION AT MUGZY INTXN OF 6000'. AS WE APCHED FORM THE NW OUT OF 20000', HE PUT OUT AIR BRAKES AND REDUCED PWR ADEQUATELY TO MAKE THE RESTRICTION. AS WE PASSED THROUGH 10000', HE RETRACTED THE AIR BRAKES AND CONTINUED TO DSND AT ABOUT 230 KTS INDICATED. I REITERATED THE XING RESTRICTION AND OUR DISTANCE TO GO WHEN WE WERE 10 MI OUT AND THEN 5 MI OUT. HE WAS NO LONGER AGGRESSIVELY GOING AFTER THE RESTRICTION. WE CROSSED MUGZY AT 7000' IN A DSNT TO 6000'. IN THE PAST, WHEN I HAVE FLOWN WITH THIS CAPT, HE HAS BEEN LACKADAISICAL ABOUT MAKING THESE RESTRICTIONS. HE IS CAPABLE OF DOING THE JOB, BUT EVIDENTLY HE DOES NOT ATTACH ANY IMPORTANCE TO THE RESTRICTIONS. ATC NEVER SAID A WORD. IT WAS I'M SURE A LOA ENTRY INTO THE NEXT SECTOR'S AIRSPACE WITH NO TFC CONFLICT. BUT WE ARE GOING TO KILL PEOPLE SOME DAY BECAUSE OF A SLACK ATTITUDE ON THE PART OF PLTS ENCOURAGED BY ATC. DO THESE RESTRICTIONS EXIST TO SEPARATE REAL TFC, OR TO EASE THE ATC WORKLOAD? HAVE I MISSED A WRITE-UP ON THIS IN YOUR NEWSLETTER?

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.