Monday, December 9, 2013

Washington state woman live-tweets husband's fatal auto accident

   Twitter.comBy M. Alex Johnson, Staff Writer, NBC NewsA Washington State woman who monitors police scanners live-tweeted a fatal car wreck Wednesday, growing increasingly frantic as she began to suspect that the victim was her own husband.Caran Johnson, who live-tweets police activity in Vancouver, Wash., under the Twitter handle @ScanCouver, began following the accident on Interstate 205 near the Oregon state line about 2 p.m. (5 p.m. ET):Very quickly, she began to fear the worst:I'm trying not to panic, but my husband left work early and he drives 205 to get home. he's not answering his phone.— CJ (@ScanCouver) December 4, 2013how long do i wait for him to come home before I call the police?— CJ (@ScanCouver) December 4, 2013Concern and sympathy began pouring in from Johnson's followers as she stayed with the increasingly traumatic story:@ScanCouver I'm sending you positive thoughts right now. I truly hope he is ok. I exited at Paden Pkwy and didn't see anyone pulled over. :[— Kirstie Hayes (@khayes1489) December 4, 2013Less than two hours after she started, Johnson reported that the victim was, indeed, her husband, tweeting simply: "it's him. he died."A trooper at the scene of a fatal car accident realized the victim's wife was live-tweeting her concerns and prevented pictures of the wreck from going out on social media so she could be informed of the tragedy in-person. KGW's Reggie Aqui reports.The Washington State Patrol and Vancouver police confirmed that Craig R. Johnson, 47, was killed about 1:40 p.m. when his Hyundai Elantra crossed the median and collided with a pickup truck. The truck driver survived but was seriously injured.Investigators said they didn't yet know what caused the accident, but Johnson tweeted that her husband had epilepsy and that he had told her he was feeling faint. You can read her entire report, which was archived on Storify by NBC station KGW of Portland:Watch the top videos on NBCNews.com

No comments:

Post a Comment