Pilot deviation, altitude overshoot.

Attributes
ACN	275060
Time
Date	199406
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : mia
State Reference	FL
Altitude	msl bound lower : 9500 msl bound upper : 10000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Jetstream 31
Operating Under FAR Part	Part 135
Flight Phase	descent other
Route In Use	arrival other enroute airway : mia
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 250 flight time total : 2400 flight time type : 250
ASRS Report	275060
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	altitude deviation : overshoot non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	flight crew : returned to intended course or assigned course
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

The captain was flying, I was the PNF. For about 30 mins beforehand, the captain was explaining (with great emotion) how the union had not fought hard enough for a better contract for the pilots during negotiations last summer (I was hired in dec). We were cleared to descend to 10000 ft from 14000 ft. I looked at the altitude selector (the jetstream has no autoplt) and noticed the 'alert' annunciation illuminated under the 10000 ft readout. The audible 'check barometric altitude' warning did not occur (it didn't go off for the rest of the flight, either. I had always considered it an annoyance, not now!) anyway, we had descended to 9500 ft when I said, '10000, we're at 9500, go back to 10000.' evidently there was no conflict. We climbed back up to 10000 ft. The controller never mentioned the deviation, nor did we bring it to his attention. Although the primary cause was simply our inattn to our altitude, other contributing factors may have been contributing, like malfunctioning altitude alerter and fatigue (we were at the end of a 7 leg, 10 hour duty day, and I was tired to begin with. In addition, I skipped breakfast and didn't have time for lunch, so I hadn't eaten in 24 hours).

Original NASA ASRS Text

Title: PLT DEV, ALT OVERSHOOT.

Narrative: THE CAPT WAS FLYING, I WAS THE PNF. FOR ABOUT 30 MINS BEFOREHAND, THE CAPT WAS EXPLAINING (WITH GREAT EMOTION) HOW THE UNION HAD NOT FOUGHT HARD ENOUGH FOR A BETTER CONTRACT FOR THE PLTS DURING NEGOTIATIONS LAST SUMMER (I WAS HIRED IN DEC). WE WERE CLRED TO DSND TO 10000 FT FROM 14000 FT. I LOOKED AT THE ALT SELECTOR (THE JETSTREAM HAS NO AUTOPLT) AND NOTICED THE 'ALERT' ANNUNCIATION ILLUMINATED UNDER THE 10000 FT READOUT. THE AUDIBLE 'CHK BAROMETRIC ALT' WARNING DID NOT OCCUR (IT DIDN'T GO OFF FOR THE REST OF THE FLT, EITHER. I HAD ALWAYS CONSIDERED IT AN ANNOYANCE, NOT NOW!) ANYWAY, WE HAD DSNDED TO 9500 FT WHEN I SAID, '10000, WE'RE AT 9500, GO BACK TO 10000.' EVIDENTLY THERE WAS NO CONFLICT. WE CLBED BACK UP TO 10000 FT. THE CTLR NEVER MENTIONED THE DEV, NOR DID WE BRING IT TO HIS ATTN. ALTHOUGH THE PRIMARY CAUSE WAS SIMPLY OUR INATTN TO OUR ALT, OTHER CONTRIBUTING FACTORS MAY HAVE BEEN CONTRIBUTING, LIKE MALFUNCTIONING ALT ALERTER AND FATIGUE (WE WERE AT THE END OF A 7 LEG, 10 HR DUTY DAY, AND I WAS TIRED TO BEGIN WITH. IN ADDITION, I SKIPPED BREAKFAST AND DIDN'T HAVE TIME FOR LUNCH, SO I HADN'T EATEN IN 24 HRS).

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.