Narrative:

Had a long day the day before, blocking 8.5 hours (flight time 7 hours) due to WX on the east coast and traffic delays at pwk. Far 135 talks about flight time not to exceed 8 hours single pilot crew, and as flight time (hobbs time) was 7 hours, I thought, incorrectly, that 10 hours rest before returning to duty was adequate. Far 1 states that 'flight time' as referred to in following sections is really block time. Due to arriving at bos at XA00 the night before, I'm sure I just suffered a 'temporary data corruption' condition. I only flew 1.8 hours block the next day and was not feeling fatigued, so I don't believe my safety or the safety of others was compromised, but this incident reinforces the need to 'cross all the T's and DOT all the I's.'

Google
 

Original NASA ASRS Text

Title: PLT EXCEEDS DUTY TIME.

Narrative: HAD A LONG DAY THE DAY BEFORE, BLOCKING 8.5 HRS (FLT TIME 7 HRS) DUE TO WX ON THE EAST COAST AND TFC DELAYS AT PWK. FAR 135 TALKS ABOUT FLT TIME NOT TO EXCEED 8 HRS SINGLE PLT CREW, AND AS FLT TIME (HOBBS TIME) WAS 7 HRS, I THOUGHT, INCORRECTLY, THAT 10 HRS REST BEFORE RETURNING TO DUTY WAS ADEQUATE. FAR 1 STATES THAT 'FLT TIME' AS REFERRED TO IN FOLLOWING SECTIONS IS REALLY BLOCK TIME. DUE TO ARRIVING AT BOS AT XA00 THE NIGHT BEFORE, I'M SURE I JUST SUFFERED A 'TEMPORARY DATA CORRUPTION' CONDITION. I ONLY FLEW 1.8 HRS BLOCK THE NEXT DAY AND WAS NOT FEELING FATIGUED, SO I DON'T BELIEVE MY SAFETY OR THE SAFETY OF OTHERS WAS COMPROMISED, BUT THIS INCIDENT REINFORCES THE NEED TO 'CROSS ALL THE T'S AND DOT ALL THE I'S.'

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.