my gf's bike keeps doing this.
its 2006 cbr 600 f4i. it does it in higher rpms. idling its fine. but once a hard load goes on it, thats it...its cuts off really hard and kinda stutters. and if i pull in the clutch right after it does that, the engine dies out. but the electronics stay on. i put it in dealer mode, and it said IAT sensor. i replaced that and it still does it. i have no idea what else to do. i am going to check the wires for the ait sensor next. after that im lost. any input people?

i cleaned her K&N changed to new plugs, checked to see if its the kick stand...and still does the same crap.

i put in the new sensor last night and rode it around with her on the back to test some extra weight, and it was running strong, then all of a sudden at like 10rpm it cut out hard & the red dash lights turned on, and i pulled the clutch in to see if it would die, and it did. but again the electronics stayed on.

(also last summer her oil light would turn on, and she had plenty oil in there. idk wtf is going on, but any input would be great.)

 

this may be too simple, but check the battery terminals... my bike did wierd things similar to yours and all it was, was the terminal wasn't tight... check that, torque it down even if it seems tight and go from there??? just a thought...hope it works out for ya!

 

thanks, but why would it give me the 9 blinks to tell me its the IAT sensor?

 

sounds like a misfire to me. You say u changed the spark plugs before or after this started happening? If i were a betting man, i would say you have either a spark or fuel issue.

 

yep changed the the spark plugs, to brand new ones.


but why would it give me the IAT sensor as an error and not just a blank screen? or a miss fire reading if there even is such a thing. its fine i was riding it hard, and i had my gf on the back, as soon as i hit like 10-11rpm it feels like a rev limiter turned on and the check engine light goes on, and i clutched it in and the bike died but the electronics stayed on.

 

becuz the ecu hasn't been reseted, so the code is still in the memory. the battery terminal is a good tip, you really should check that out.