Blocked Extra point muffed by K in endzone

[zoom]

 Hello everyone,

  I am a high school official in Connecticut (NFHS) but prep schools use NCAA rules.
 
Yesterday we had the following play.  A's Extra point attempt is blocked by B74 behind the LOS.  The kick is muffed by A41 at the A4 yard line and the ball rolls into the endzone.  B91 tries to recover the ball there but muffs it and K71 recovers the ball in the endzone.  We ruled it was a good conversion, 2 points, for the following reasons:

All touching behind the LOS is ignored on a scrimmage kick.
The kick was first touched by R beyond the neutral zone, meaning either team is eligible to possession. 

I don't have a NCAA book, so I was hoping to get feedback here.

Thanks!

[maven]

If a scrimmage kick goes into B's EZ untouched by B beyond the NZ, the ball is dead when it touches the ground in the EZ. NCAA 6-3-9

B's touch behind the NZ is ignored. Unless B91 touched the ball in the EZ before it touched the ground (you said it was rolling), you should have killed it when the kick touched the ground in the EZ. B91 muffed and A71 recovered a dead ball.

Tough to get all the rules differences, especially if only a few of your games use the other code.

[Morningrise]

You say it rolled into the end zone. The ball should be dead at that point, because it is a scrimmage kick that touches the ground in the EZ without having been touched by Team B beyond the NZ. (B74's blocking of the kick is considered by rule to be within the NZ, not beyond it, regardless of where it really happens.)

Now, if B91 touched it outside the EZ, or perhaps touched it the EZ on the fly before it rolled or bounced there, then all bets are off. It's no longer dead when it hits the ground in the EZ. It belongs to whomever recovers it. Then A71 would score two points.

It's correct that A41's touching behind the NZ is immaterial, because the kick at that time had not crossed the NZ. All Team A players may legally touch the kick before it crosses the NZ.

[zoom]

Thanks gentlemen.  I learned a lot from your posts.  We'll get it right next time.