Offensive line coach Bill Durkin.
BLADE/JETTA FRASER Enlarge
BOWLING GREEN – A Bowling Green State University football coach is on administrative leave after a pair of driving incidents, including a drunken-driving charge, that took place last weekend.
Bill Durkin, the Falcons offensive line coach, was not with the team for BGSU’s 34-7 victory over Tulsa at Doyt Perry Stadium on Thursday. After the game, BGSU officials indicated that Mr. Durkin was on administrative leave but declined further comment.
According to records from the Bowling Green post of the Ohio Highway Patrol, Mr. Durkin, 42, of Perrysburg, was arrested at the East Wooster Street exit of I-75 at 2:54 a.m. on Aug. 24 and charged with operating a vehicle while under the influence. He also was charged with a marked lanes violation.
Later that morning, Durkin was involved in an injury accident at the intersection of Hull Prairie Road and Five Point Road, outside of Perrysburg.
At 11:20 a.m., Ohio Highway Patrol records indicate that Mr. Durkin was northbound on Hull Prairie Road when his vehicle was struck by Eleanor Bebo, who was driving eastbound on Five Point Road and reportedly failed to stop at the stop sign.
Mr. Durkin’s vehicle went off the road and struck a tree following impact. Ms. Bebo’s vehicle went off the road and struck a stop sign.
Ms. Bebo was cited for failure to yield and was at fault in the accident.
Mr. Durkin was cited for driving under suspension as a result of the drunken-driving arrest earlier in the day.
Mr. Durkin entered a not guilty plea during a first appearance hearing on Monday. He is scheduled to appear in Bowling Green Municipal Court on Sept. 4 at 9:30 a.m.
Guidelines: Please keep your comments smart and civil. Don't attack other readers personally, and keep your language decent. Comments that violate these standards, or our privacy statement or visitor's agreement, are subject to being removed and commenters are subject to being banned. To post comments, you must be a registered user on toledoblade.com. To find out more, please visit the FAQ.