Monday, April 21, 2014
A Fulton man turned himself in after allegedly leading police on a high-speed chase Saturday night.
The Fulton Police Department received a report at 8:20 p.m. Saturday of a white Chevrolet Corvette driving carelessly near Lynn and Washington avenues. An FPD press release states that officers arrived in the area, found the vehicle backing into a private drive and identified the driver as Christopher Wallace, 28. Officers allege Wallace continued to roll forward as officers attempted to speak to him, and Wallace eventually took off at a high rate of speed northbound on Business 54.
Another patrol unit fell in behind the vehicle, and the release state the pursuit exceeded 90 mph as it turned southbound onto Route C.
The release states the officer lost sight of the vehicle near the south city limits, but another vehicle found the vehicle parked on Merklin Drive "with a large amount of smoke or vapors coming from the vehicle."
Officers say witnesses at the scene saw Wallace enter a residence off of Route C and officers found the back door to be open. The release states that a search revealed the house was unoccupied at the time and Wallace had fled via another entrance.
Officers confirmed the vehicle was registered to Wallace and towed it to the police department for processing.
At about 1:30 p.m. Sunday, Wallace was brought to the police department by a family member. He was issued summons for resisting arrest by flight, interfering with an arrest, careless and imprudent driving and failure to yield to an emergency vehicle. He was transported to the Callaway County Jail on $6,500 bond, which he posted.
More like this story
- Fulton man arrested after high-speed chases in Jefferson City, Cole County
- Fulton man caught after chase
- Portland man arrested on slew of traffic charges, threatening an officer
- Auxvasse man arrested after accident reveals pot, gun
- Local man charged with assault on a law officer after a high-speed pursuit through Camden County
Use the comment form below to begin a discussion about this content.
Please review our Policies and Procedures before registering or commenting