Commuter has altitude deviation and gives wrong ATIS identify due to fatigue.

Attributes
ACN	251047
Time
Date	199309
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : crw
State Reference	WV
Altitude	msl bound lower : 5000 msl bound upper : 8000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	descent other
Route In Use	enroute airway : crw
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 300 flight time total : 5000 flight time type : 3500
ASRS Report	251047
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	altitude deviation : overshoot non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On descent to charleston, wv, ZID handed us off to crw approach. On initial contact with approach, I stated our altitude (11000 ft) and that we had ATIS information. The controller gave us a descent to 8000 ft which I read back along with a change in assigned heading. During the readback I realized I had stated the atl departure ATIS which was written on the weight and balance form. I found the correct ATIS information code and advised approach that we had that information instead. Meanwhile, the captain set the altitude alerter to 3000 ft instead of 8000 ft. After fumbling with the paper work I confirmed the incorrect altitude. The controller questioned us as we were descending through 5000 ft. I attribute the mistake to fatigue. My company is short of pilots and I've flown in excess of 100 hours in august and near 100 hours in july. 2 nights before this incident I got 5 hours of sleep on my 8 hour reduced rest overnight. The night before this incident, I didn't go to sleep until PM00 for an XA38 am sign-in. So I had bout 10 hours rest for 2 nights prior to this mistake. I believe part 135 rest requirements are inadequate. The 34 in 7 rule and the 120 hour month rule do not provide crews with sufficient rest.

Original NASA ASRS Text

Title: COMMUTER HAS ALTDEV AND GIVES WRONG ATIS IDENT DUE TO FATIGUE.

Narrative: ON DSCNT TO CHARLESTON, WV, ZID HANDED US OFF TO CRW APCH. ON INITIAL CONTACT WITH APCH, I STATED OUR ALT (11000 FT) AND THAT WE HAD ATIS INFO. THE CTLR GAVE US A DSCNT TO 8000 FT WHICH I READ BACK ALONG WITH A CHANGE IN ASSIGNED HDG. DURING THE READBACK I REALIZED I HAD STATED THE ATL DEP ATIS WHICH WAS WRITTEN ON THE WT AND BAL FORM. I FOUND THE CORRECT ATIS INFO CODE AND ADVISED APCH THAT WE HAD THAT INFO INSTEAD. MEANWHILE, THE CAPT SET THE ALT ALERTER TO 3000 FT INSTEAD OF 8000 FT. AFTER FUMBLING WITH THE PAPER WORK I CONFIRMED THE INCORRECT ALT. THE CTLR QUESTIONED US AS WE WERE DSNDING THROUGH 5000 FT. I ATTRIBUTE THE MISTAKE TO FATIGUE. MY COMPANY IS SHORT OF PLTS AND I'VE FLOWN IN EXCESS OF 100 HRS IN AUGUST AND NEAR 100 HRS IN JULY. 2 NIGHTS BEFORE THIS INCIDENT I GOT 5 HRS OF SLEEP ON MY 8 HR REDUCED REST OVERNIGHT. THE NIGHT BEFORE THIS INCIDENT, I DIDN'T GO TO SLEEP UNTIL PM00 FOR AN XA38 AM SIGN-IN. SO I HAD BOUT 10 HRS REST FOR 2 NIGHTS PRIOR TO THIS MISTAKE. I BELIEVE PART 135 REST REQUIREMENTS ARE INADEQUATE. THE 34 IN 7 RULE AND THE 120 HR MONTH RULE DO NOT PROVIDE CREWS WITH SUFFICIENT REST.

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.