Lead contamination in Washington, D.C. drinking water

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lead contamination in Washington, D.C. drinking water, first discovered in 2001, left thousands of children with lifelong health risks, and led to a re-evaluation of the use of chloramine in public drinking-water systems. Professor Marc Edwards, an expert in plumbing corrosion, discovered lead levels at least 83 times higher than the accepted safe limit while performing research into premature pipe corrosion for the District of Columbia Water and Sewer Authority (WASA). He found that the decision to change from chlorine to chloramine as a treatment chemical had caused the spike in lead levels.

After the Washington Post ran a series of front-page articles about Edwards's findings, resulting in widespread public concern, the United States House of Representatives conducted an investigation. The House found that the U.S. Centers for Disease Control and Prevention (CDC) had made "scientifically indefensible" claims in a report that had indicated there was no risk from the high lead levels. The Post investigation uncovered evidence of widespread misreporting of lead levels at water agencies across the United States, leading to regulatory crackdowns and changes in Environmental Protection Agency policies.

The problem was addressed in 2004 by adding additional treatments to the water, preventing the chloramine from dissolving lead in the water mains, solder joints, and plumbing fixtures.

In 2010, the CDC reported that 15,000 homes in the Washington, D.C. area might still have water supplies with dangerous levels of lead.

2001–2004: Initial reports of elevated lead

In 2001, more than half the water samples taken from 53 DC-area homes under the procedures required by the EPA's Lead and Copper Rule showed levels of lead exceeding the national standard of 15 parts per billion (ppb).[1] Lead disrupts the physical and mental development of fetuses, babies, and young children, and can cause kidney problems and high blood pressure in adults.[1] The rule does not assume that there is a "safe" level of exposure, but notes that 15 ppb is an "action level" where utilities must take action.[1] The rule was created in 1991, after research showed that drinking water could account for one-fifth of all lead intake.[1] Lead is not normally present in drinking water; it is released from the inside surface of lead service lines (pipes that run from the main to the house), joints connected with lead-based solder, and lead fixtures inside the house. Based on these findings, WASA was required to notify the public and implement plans to replace lead service lines in key areas of the municipal water system.

The first media attention came in late 2002, when the Washington City Paper ran an article about a resident of American University Park whose water tested six to 18 times the EPA Lead and Copper Rule's action level.[2] WASA found that homes in its service area with lead service lines averaged five times the EPA limit for lead during a year-long period.[2] The results were unexpected; the EPA scientist overseeing DC's water suggested that drought conditions might have raised the alkalinity levels of the Potomac River, leading to a change in the pH of the water.[2] As a result, WASA was required to start replacing seven percent of the district's lead service lines each year until the levels dropped below 0.015 milligrams per liter.[2] At the time, about 23,000 WASA customers had lead service lines.[3]

In March 2003, Marc Edwards, a professor of civil engineering and expert on corrosion in drinking-water systems, was conducting research into an unexpected increase in pinhole leaks in copper water pipes in the DC area. WASA funded Edwards's research.[4] Suspecting the leaks were caused by a change in the water chemistry, Edwards used a field meter to test for lead in one home's water. The meter could read values up to 140 ppb. His initial reading pegged the meter, so he diluted the sample to ten percent of its original strength. Even so, diluted, the sample still pegged the meter,[5] indicating the water contained at least 1,250 ppb of lead.[6] "Some of it would literally have to be classified as a hazardous waste," Edwards said.[5]

After Seema Bhat, a water quality manager at WASA, told her superiors at the agency and at the EPA about the lead levels and warned that federal guidelines required aggressive action, she was fired by the agency. A federal investigator found that she had been improperly terminated.[3]

The lead levels required WASA to conduct a wider survey of their water quality. By the fall of 2003, it had tested more than 6,000 homes in the District, finding that two-thirds tested had more than 15 ppb of lead in their water.[3] The survey showed that over 4,000 homes served by WASA had lead levels exceeding the acceptable level.[7] More than a third of the homes surveyed—2,287 out of 6,118—had levels exceeding 50 ppb.[3] The water tested over 300 ppb in 157 homes.[1] Despite this result, WASA did not notify its customers of the risk until November 2003.[7]

Although regulations required WASA to include the specific warning "Some homes in this community have elevated lead levels in their drinking water. Lead can pose a significant risk to your health." in the water bills of each affected customer, WASA's notice omitted key parts of the phrase such as "in their drinking water" and "significant".[7] Although Federal law required WASA to hold public meetings to discuss the problem and actions people could take to protect themselves, they advertised the meetings as being "to discuss and solicit public comments on WASA's Safe Drinking Water Act projects", omitting mention of lead.[8] The EPA was required to review the notice before it was sent out; one D.C. Council member, commenting on the EPA's approval of the faulty notice, asked "Where were you, EPA?"[1] The EPA later found that WASA's notice violated federal law because of the omissions.[9]

In January 2004, the Washington Post reported that the mayor and several D.C. Council members had not been informed of the elevated lead levels.[8] The Washington City Paper said that Carol Schwartz, the councilmember who chaired the Committee on Public Works and the Environment, was not informed of the lead issue until that newspaper contacted her during the last week of January 2004.[3] Early communications from WASA limited the health advisory to pregnant women and small children in homes with lead service leads, but later tests showed the high lead levels were also present in homes with copper service leads.[7]

Meanwhile, on January 2, 2004, WASA called Edwards and threatened to cut off his access to monitoring data needed for his research, and divert funding from him to other researchers, unless he stopped working with the homeowners whose water showed high lead levels.[5] Soon after, the EPA discontinued its own contract with Edwards.[5]

2004: Washington Post

The issue became front page news when the Washington Post ran an article titled "Water in D.C. Exceeds EPA Lead Limit" on January 31, 2004 across six columns of page A1.[8][10] Reporter David Nakamura was contacted by one of the homeowners whose water was tested by WASA during its survey after he received the test results.[1] Nakamura—who had no prior experience with clean water issues—initially thought it was a minor issue, but agreed to help the homeowner get a response from WASA.[10] When WASA would not give him a straight answer, Nakamura pressed them for full data on the tests.[10] Nakamura says that, even though he was "stunned" at the facts reported in that first story, the Post "had no idea about the size and scope of what was to follow."[10]

The article quoted Erik Olson, an analyst for the Natural Resources Defense Council, as saying "This is a really big deal... If schools go over 20 parts per billion, they immediately take the water out of production."[8] WASA recommended that residents let the tap run for 30 seconds to one minute before using it to reduce the risk.[8]

This first Post article was the first public mention of the theory that the lead levels were tied to chloramine. The traditional use of chlorine had been stopped four years earlier, out of concerns that it could produce harmful chemicals in the pipes.[8] Long-term exposure to the byproducts from chlorine treatment has been linked with cancer.[11] The paper quoted officials as saying that it was possible chloramine was more corrosive to lead pipes.[8] (In fact, the Army Corps of Engineers, which is responsible for the Washington Aqueduct that supplies water to WASA, rejected a recommendation to add phosphates to the water to prevent lead leaching in the mid-1990s.)[1] The change to chloramine was made after the EPA issued regulations concerning disinfection byproducts formed when chlorine reacts with organic matter in drinking water; the EPA considered these byproducts to be a potential health threat.[12]

After the first article, the Post formed a core team of reporters to investigate the issue. Nakamura was joined by reporters Carol Leonnig, Jo Becker, Avram Goldstein, and D'Vera Cohn; editor Marcia Slacum Greene provided daily oversight.[1] Nakamura was the lead reporter for the breaking news coming from WASA and City Hall, and wrote profiles of key players.[10] Leonnig reported on the federal and EPA response to the contamination.[10] Cohn investigated the Washington Aqueduct angle and worked with water quality and environmental experts.[10] Goldstein covered the DC Department of Health.[10] Becker looked at water quality nationwide.[10]

After the first article appeared, residents inundated WASA's water hotline with calls and overwhelmed water testing laboratories with requests to have their tap water tested for lead contamination. District elected officials immediately called for an emergency public meeting, and established an inter-agency task force with the EPA to investigate and manage the problem.[7] However, messages to the public at the time were often confusing and contradictory: while WASA was suggesting running taps for 90 seconds to flush out any lead, the EPA was demanding that recommendation be changed to ten minutes.[7]

The Post article lead WASA to hand out over 30,000 free water filters, hire health experts, and offer free blood tests to residents.[1] Some water fountains were turned off due to lead levels.[1] In 2004, the D.C. Council held 11 oversight hearings on the issue; the US Congress held four.[1] American University claimed that its water was safe to drink, because the larger water mains feeding commercial sites like the college were not made of lead.[13]

After Nakamura's first few stories for the Post on the issue, he was contacted by Seema Bhat's attorney.[10] Bhat, who was then fighting her dismissal from WASA, shared thousands of internal documents with Nakamura.[10] The documents, Nakamura said, "provided a fairly clear picture" that WASA had been trying to find a way to avoid the cost of replacing pipes and adding additional chemicals to the water.[10] He said Bhat's documents were critical to the Post's investigation.[10] He recalls that, while reading the documents, the team found WASA memos indicating that they tried to find "clean" houses to test to reduce the apparent average lead level from the testing, but the more they tested, the more "dirty" houses they found.[10]

By April 2004, there were reports of some DC-area homes reaching lead levels of 6,000 ppb to 48,000 ppb.[14][15]

In June 2004, the EPA cited WASA for a "serious breach" of the law, including withholding six test results showing high lead levels in 2001, dropping half of the homes that had previously tested high for lead levels in subsequent testing, and avoiding homes known to be at high risk for contamination.[16] In July, a WASA-commissioned report supported the Post's claims that the agency had known about the high lead levels for years, but had failed to notify regulators or the public.[17]

A DC WASA lead service line being replaced in 2008.

In August 2004, the Army Corps of Engineers started adding orthophosphate to the water in hopes of preventing lead leeching.[18][19] By November, WASA's board of directors had committed to a plan that would replace all of the agency's 23,000 lead pipes by 2010, at a cost of $300 million—starting with 2,800 lead pipes to be replaced in 2005.[18] WASA estimated that the repairs would cost residents $6 to $7 a month.[20] The agency was not legally responsible for the portion of the lead service lines within a homeowner's property lines; however, they offered to perform the work at a set rate, and arranged a low-interest loan program with Wachovia Bank to help homeowners afford the cost.[18]

By January 31, 2005, the Post had run over 200 stories on the issue, amassing thousands of pages of correspondence through the Freedom of Information Act.[1] Gloria Borland, a District resident, testified before Congress: "If the [Washington] Post had not exposed this scandal, our children today would still be drinking lead contaminated water".[14]

Post reporters Nakamura, Leonnig, Cohn, Becker, Craig Timberg, Monte Reel, and Sarah Cohen won the 2005 Selden Ring Award for Investigative Reporting for the articles.[21] Michael Parks, director of USC Annenberg's School of Journalism and Pulitzer Prize-winning former editor of the Los Angeles Times, said "The Washington Post's work was a very important piece of journalism—important to every man, woman and child living in the District of Columbia, drinking its water and thinking it was pure. And it was important to the residents of other cities whose water is contaminated by lead and other toxic substances".[21] The award's cash prize of $35,000 is believed to be the largest in journalism.[22] According to Nakamura, some at the Post were surprised to win the award, because of the atypical nature of the Post's investigation. Most winners conduct a long-term investigation and then publish long articles over a few days with the results; the Post covered the investigation as a series of beat stories.[10] Nakamura said he had never heard of the Selden Ring Award until the day his editor told him that the team had won it.[10]

2004: The CDC report

On March 30, 2004, an "MMWR dispatch", Blood Lead Levels in Residents of Homes with Elevated Lead in Tap Water --- District of Columbia, 2004, was made available on the MMWR web site. It was then published by CDC as "MMWR Weekly, April 2, 2004 / 53(12);268-270".[23] The report "summarizes the results of the preliminary investigations, which indicated that the elevated water lead levels might have contributed to a small increase in blood lead levels (BLLs)". The report describes the background, and the various kinds of blood tests it employed, and explicitly states: "All blood tests were used in this analysis." There is no mention at all of any test results not being available, not even in the caveat section, where other potential sources of error are discussed.

The report concludes that the high amounts of lead in the drinking water may have led to a slight rise of the blood levels; however, not to the levels of official concern. It also claims that the average levels were sinking. However, the report notes that there is no known "risk free" level, and therefore recommends that efforts should be made to eliminate lead in children's blood entirely.

The report later was strongly criticized, both by Marc Edwards and by the United States House Committee on Science, Space and Technology; see § Congressional review of the 2004 CDC paper.

2004–2005: Government hearings

At an oversight hearing before the House Committee on Government Reform in early March 2004, Marc Edwards testified that his studies showed the change from chlorine to chloramine was the cause of the elevated lead levels.[24] He stated that the chloramine-treated water was leaching lead not only from the old lead lines, but also from brass fixtures in homes.[24] Brass is made with lead; even brass classified as "lead free" under the Safe Drinking Water Act can contain up to eight percent lead.[24] Edwards said that this could be the cause of the high lead levels in areas where WASA did not use lead lines.[24] He also cautioned that replacing lead service lines with copper could make the problem worse; newly installed copper lines could react with the chloramine in a way that would increase corrosion of the remaining lead lines in the system.[24] The chief of the Washington Aqueduct disagreed, saying that tests taken after the chloramine treatment commenced didn't show any additional corrosiveness.[24] He believed corrosion inhibitors, like orthophosphate, could be added to the water to prevent lead leaching.[24] In the spring of 2004, a temporary switch from chloramine back to chlorine for annual pipe flushing caused a 25 to 30 percent drop in lead levels, lending credence to the chloramine theory.[11][25] In one home that was tested by WASA before and after the switch, lead levels dropped tenfold.[11]

On March 23, 2004, Anthony A. Williams (the mayor of the District of Columbia) and Carol Schwartz (chair of the DC Council's Committee on Public Works and the Environment) wrote a letter to President George W. Bush, asking the federal government to reimburse WASA $24,093,700 and the District of Columbia $1,730,401 to cover expenses from the lead contamination.[26] The letter justified the request for full reimbursement by saying "the regulatory decisions of EPA appear to have generated these costs" and that it would be "inherently unfair" for taxpayers and WASA customers to pay those costs.[26] In 2005, President Bush proposed cutting the EPA's budget by almost a half-billion dollars, mostly from clean-water programs.[27] He wanted to decrease spending on replacing aging water facilities by 83 percent.[27]

On March 30, 2004, the Centers for Disease Control and Prevention (CDC) published a Morbidity and Mortality Weekly Report (MMWR) that found the lead "might have contributed a small increase in blood lead levels."[28] The report claimed that no children with dangerously high blood lead levels were found, even in the homes with the worst lead levels.[29] Officials in other cities, such as New York and Seattle, cited the report as justification for a less-than-aggressive response to high lead levels in their own water.[28] Water testing in the first six months of 2004 showed 90 percent of homes having 63 ppb of lead or less in the water.[30]

In October 2004, Edwards co-authored an article in the Journal of the American Water Works Association that linked chloramine use with greatly increased lead leaching.[31]

A report commissioned by the D.C. Council released on December 8, 2004 faulted the federal government's regulation of the city's water supply as a factor in the lead contamination. The report noted that no one agency was responsible for the water quality: The Army Corps of Engineers treated the water, WASA delivered it, and the EPA performed the quality checks.[32] It urged the Council to assume authority for the entire system.[32] In the last six months of 2004, 90 percent of homes tested had lead levels of 59 ppb or lower.[30]

The city's interim inspector general, Austin A. Andersen, released a report on WASA's performance in January 2005. Andersen called for WASA to enter a formal agreement with the city's Health Department to ensure that future communications about water health issues were timely and worded appropriately.[9] WASA rejected the need for such an agreement.[9] That same month, the Architect of the Capitol issued a warning to Capitol Hill employees that they should not use water from bathroom or kitchen faucets for drinking or cooking.[33] Some water fountains on the campus were turned off, although employees were told it was okay to continue using the others.[33] One home on Capitol Hill was found to have 308 ppb of lead in 2003.[34]

On January 21, 2005, the EPA ordered WASA to notify more than 400 homeowners that the agency had mistakenly told them their house's water lead levels were safe, and to replace an additional 500 service lines to comply with federal law.[30] The EPA said that WASA had flushed the water line for five minutes before running the lead tests for those homes, resulting in artificially low readings; such a lengthy flush is not permitted by EPA standards.[30] The EPA did not believe that the flushes were done intentionally by WASA to reduce lead levels.[30] The testing had been done as part of an effort to avoid the expense of replacing lead lines in areas where it found low lead levels.[30]

2004: Other cities investigated

In 1999, an EPA survey estimated that the United States's drinking-water systems were in need of $150 billion worth of repairs over the following 20 years.[20] However, in April 2004, an EPA spokesperson told the Washington Times that "high lead levels are not a pervasive problem".[20] At a Congressional hearing that month, the EPA testified that it had no current information on lead levels in 78 percent of the nation's water systems, and that as many as 20 states had not provided any data.[14]

On October 5, 2004, the Washington Post ran a front-page article reporting that cities across the United States were illegally manipulating lead testing results, such as discarding high readings or avoiding homes likely to have high readings.[16] A former EPA official described it as "widespread fraud and manipulation" on the part of water utilities.[16] That July, however, an EPA administrator told Congress that "we have not identified a systemic problem".[16] Using data from the EPA, the Post identified 274 utilities that had reported unsafe lead levels between 2000 and 2004.[16] Some utilities defended their testing practices as being approved by state regulators; others argued that the lead was actually leaching from customers' fixtures, not their plumbing.[16]

Among the cities that the Post faulted through the EPA data were:[16]

  • Boston, where state regulators discovered that at least one quarter of the locations tested were not at high risk for lead contamination;
  • Detroit, where the utility failed to test required high-risk homes;
  • New York City, which reported lead falling to safe levels in 2000—but omitted 300 test results that would have marked the water as unsafe in 2001 and 2002 if reported;
  • Philadelphia, which could not produce documentation for their decision to discard a high test result from 2002—despite being required by federal law to do so—that would have put the city over the EPA limit if it had been included;
  • Lansing, Michigan, which discarded four tests that would have put the city's water over the limit because the homeowners supposedly did not follow the proper directions in collecting the samples—even though the law prohibits doing so;
  • Ridgewood, New Jersey, which removed "hot" houses from its testing after exceeding the safe limit in 2000;
  • Providence, Rhode Island, where high levels were found in 2002, failed to inform the public as required and instead waited more than the legal limit of four months to test again;
  • Seattle, where state regulators allowed the utility to miss a 1997 deadline to reduce the corrosiveness of its water by six years, allowing high lead levels to persist during that period;
  • Portland, Oregon, where the city and state decided to launch a lead-danger educational campaign instead of building a treatment plant as required by law—and the EPA later suggested the utility drop urban homes with high lead levels from its testing and replace them with suburban homes with significantly lower levels.

The Post article led the United States Attorney for the Southern District of New York to open an investigation into the city's drinking-water lead levels.[35][36] Regulators in Michigan and Oregon also investigated utilities singled out by the Post in those states.[36] Senators James M. Jeffords and Paul S. Sarbanes called for the EPA to impose tougher standards; Jeffords and Senator Hillary Rodham Clinton called for an investigation of the EPA following the Post's findings.[37]

Seattle had already suffered widespread lead contamination in its public school system in 2003. One parent, a scientist who had initiated the investigation there, said "we continue to suffer from an epidemic of lead complacency" nationwide.[38]

The EPA said that between 2003 and 2005, only four large water systems had unsafe lead levels: Washington, DC; St. Paul, Minnesota; Port St. Lucie, Florida; and Ridgewood, New Jersey.[27]

2005–2006: Lower lead levels

By January 2005, a year after the high lead levels were publicized by the Post, advocates were calling for the firing of local and federal officials involved in the issue, saying that they had done too little to fix the problem.[39] Eric Olsen of the Natural Resources Defense Council said that officials "have fallen down on the job" because thousands of residents still had unsafe water.[39] The group Lead Emergency Action for the District called for an overhaul of WASA's management, an independent study of needed improvements to the water system, stronger laws, and action from the EPA.[39] "We want fines and a criminal review," said Olsen.[39]

In March 2005, the EPA proposed changes strengthening the Lead and Copper Rule. The changes require utilities to give test results directly to homeowners, and to notify state and federal regulators before changing water-treatment methods.[40] Critics, such as Clean Water Action, called the changes "revisions at the margins".[40] Rick Maas, co-director of the Environmental Quality Institute at the University of North Carolina, said the revisions would "solve maybe 5 to 10 percent of the problem" with the Rule.[40] Trade organizations, such as the American Water Works Association, found the changes "basically reasonable".[40]

That month, WASA said that recent tests showed encouraging declines in lead levels, which it attributed to the orthophosphate treatments started in August 2004.[25] Out of 51 homes tested, only four had readings above 15 ppb; ten of those homes were above the 15-ppb standard the previous year, but fell below it in this test.[25] WASA also noted that the Army Corps of Engineers would continue using chloramine throughout the year to keep the water chemistry stable.[25] By May 10, 2005, the company was announcing that its tests were "below the '90th percentile lead action level.'"[41]

As of January 2006, WASA said that about 29 percent of its customers had chosen to replace the lead service lines within the customer's property.[42] In a January press release, WASA said that the average lead level in its most recent tests was 7 ppb.[43] The authority also claimed that a voluntary blood-lead-level screening it funded showed no identifiable public health impact from the elevated lead levels.[43]

The EPA formally reduced its oversight of WASA in May 2006, after testing showed the lead levels had remained below 15 ppb for a full year.[42] However, the agency continued to require WASA to submit 100 samples every six months for at least another year; the normal requirement is 50 samples a year.[42]

Even after the lead levels abated, the Post continued to note other problems with the District's water supply. In 2007, it noted that WASA's periodic "chlorine surge" resulted in high levels of haloacetic acids, a chlorine disinfection byproduct believed to be unsafe.[44] Utilities use annual or biannual chlorine surges to remove pathogens such as cryptosporidium that are not adequately killed by chloramine.[44] Independent testing by the Environmental Working Group showed 40 percent of samples exceeded federal safety limits for chlorine byproducts, but officials from the Washington Aqueduct and WASA said the levels were probably temporary and that the water was safe to drink.[45]

2006–2010: EPA, CDC, expert reports faulted

In January 2006, the Government Accountability Office released a study criticizing the EPA's efforts monitoring lead levels in drinking water across the United States.[46] Although the study found that lead in drinking water had generally declined since the 1990s, it noted that data collection problems "may be undermining the intended level of public health protection".[46]

Guidotti paper

In 2007, the journal Environmental Health Perspectives published a paper about the public health response to the lead contamination, written by a team of academic investigators headed by Tee Guidotti of George Washington University.[47] Guidotti and his team had been hired as consultants by WASA in 2004;[48] he had told the WASA board that water only accounts for seven percent of the typical two-year-old child's lead exposure.[49] The paper analyzed data from the 2004 screening program, identifying sources of confounding or bias. Four indicators were examined, and none showed evidence that blood lead levels had been affected by the elevation of lead in drinking water. The investigators concluded that the evidence did not clearly demonstrate a correlation between lead in the District's drinking water and blood lead levels. However, they cautioned that a population study was not suitable for establishing such relationships. They called for reduction in exposure from water as well as from other sources.[47] The paper stated "There appears to have been no identifiable public health impact from the elevation of lead in drinking water in Washington DC in 2003 and 2004."[50]

The Guidotti paper was called into question by members of the DC Council in February 2009, after the Washington Post ran an article about a more recent study by Marc Edwards that found a correlation between water and blood lead levels in area children.[51] The National Institutes of Health, publisher of the journal in which the paper appeared, were unaware that George Washington University's contract with WASA gave the water authority final approval over anything Guidotti wrote concerning the authority.[52] Guidotti was also supposed to remove the sentence about public health impact from the paper before publication, because experts reviewing the paper had rejected that finding; he failed to do so.[52] Guidotti and WASA both denied that the agency influenced the paper;[52] Guidotti said he didn't view the contract as giving WASA preapproval over the paper, and therefore didn't disclose it to the journal.[53] In an August 2006 e-mail obtained by the Post from Edwards, Guidotti agreed to replace the sentence with "Measures to protect residents from exposure to lead in drinking water may have prevented more frequent elevations in blood lead" before its publication, but that did not happen.[53] The journal refuses to accept research that is under a sponsor's control; it conducted a review to determine if the paper should be retracted—the journal's first such review in its 30-year history.[53] The paper had been cited as evidence that the lead contamination had not harmed District residents.[53]

In an e-mail to the Washington City Paper, Guidotti refuted any claims that WASA influenced the team's findings. He clarified that WASA's contract was with the university, not Guidotti personally. He said "The data in our 2007 study are valid, the analysis was accurately reported, and we stand by the conclusions."[54]

The review panel convened by Environmental Health Perspectives released its findings in June 2009, finding that the controversial sentence was included due to "inattention to detail" and found no evidence that Guidotti was trying to mislead readers.[50] The panel recommended that Guidotti submit an apology and correction; he did so.[50] The panel said it found evidence that neither Guidotti nor WASA intended for the utility to exercise approval over the research conclusions.[50]

Edwards paper

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The March 1, 2009 issue of Environmental Science and Technology included a paper by Marc Edwards, Simoni Triantafyllidou, and Dana Best that established a link between the elevated lead levels in the drinking water and potentially harmful blood lead levels in area children.[55] The Washington Post announced the results of that study on January 27, 2009.[56] The report found that 42,000 children who were in the womb or under age 2 during the contamination are at risk of health and behavioral problems.[56] In some areas, the number of children with enough lead to cause irreversible IQ loss and developmental delays more than doubled between 2000 and 2003.[56] These findings contradicted previous statements by WASA that there were no health impacts, as well as the 2004 CDC MMWR report.[56] David Bellinger, a Harvard University neurologist, told the Post, "If these data were available previously, I would be surprised that anyone would be assuring the public there was no problem."[56]

The CDC refused to provide Edwards with the data necessary to perform the study.[57] He convinced the Children's National Medical Center to share the data with him in 2008.[57]

The paper won the Editor's Choice Award for Best Science Paper of 2009 from the editors of Environmental Science and Technology.[58]

Congressional review of the 2004 CDC paper

Edwards's study raised new questions about the March 2004 CDC Morbidity and Mortality Weekly Report that downplayed the health impact of the lead contamination. Salon noted that the CDC had found a link between lead pipes and high childhood blood lead levels in the district in 2007, but did not publicize the study.[28] The principal author of the 2004 study—Mary Jean Brown, who co-authored the 2007 study—acknowledged that thousands of blood tests were missing from the 2004 study, but defended the paper's conclusion that any harm was slight.[28] "There is no indication that DC residents have blood lead levels above the CDC levels of concern", she wrote.[59]

However, Edwards's results came from analysis of the same data used for the 2004 CDC report. When he wrote to the CDC's associate director of science, questioning the report's conclusions and methodology, he received a belated reply: "We have examined CDC's role in the study and have found no evidence of misconduct."[28]

The United States House of Representatives' Science and Technology Committee opened a congressional investigation into the 2004 CDC report.[59] Investigators found that although the CDC and city health department reported dangerous lead levels in 193 children in 2003, the actual number was 486 according to records taken directly from the testing laboratories.[59] Representative Brad Miller of North Carolina called the CDC report's data "wildly incomplete".[59] The underreported results came from the city's health department, which had said the missing tests were omitted because some labs did not report low lead levels to the city.[59] The health department data was also the basis for Guidotti's paper.[59]

The investigation found that the CDC knowingly used flawed data in drafting the report, leading to "scientifically indefensible" claims in the 2004 paper.[60] It also cited the CDC for failing to publicize later research showing that the harm was more serious than the 2004 report suggested.[60] After the investigation's findings were released, the CDC initially stood by the report's findings that no significant harm was caused by the lead, but acknowledged that the claim that no children with lead poisoning had been found was "misleading".[60] Edwards called for the CDC to retract the paper and for Brown's resignation.[60] "If you were a child living in D.C. at that time, a single glass of tap water could have elevated your blood lead to unsafe levels," said Edwards.[61]

The report strongly criticized Brown for failing to check the original lab results.[60] It also noted that one section of the 2004 CDC report said not one of the people living in a home with water lead levels 20 times higher than the action level had elevated blood lead, but it failed to mention that most of those people were drinking bottled or filtered water, not tap water, before their blood was tested—a fact Brown and her co-authors were well aware of.[60] The investigation found that Brown gave her fellow authors just three hours to review her work before it was submitted for publication.[61]

A year after the Washington Post published the results of the investigation, the CDC published a "Notice to Readers" in the May 21, 2010 issue of the Morbidity and Mortality Weekly Report admitting that the 2004 report was misleading.[62] It said the original report "did not reflect findings of concern from the separate longitudinal study that showed that children living in homes serviced by a lead water pipe were more than twice as likely as other DC children to have had a blood lead level ≥10 µg/dL."[62] A further Notice to Readers published in June 2010 clarified that the results in the 2004 report "should not be used to make conclusions about the contribution of water lead to blood levels in DC, to predict what might occur in other situations where lead levels in drinking water are high, or to determine safe levels of lead in drinking water."[63]

The Post described the CDC's Notice to Readers as "a full vindication" for Edwards, who spent tens of thousands of dollars out of his own pocket to fund his research, and who was the target of attempts to besmirch his professional reputation by the CDC and EPA.[57][61] Tom Sinks, the deputy director of the CDC's national center for environmental health, told the Post "Looking backward six years, it's clear that this report could have been written a little better".[57]

In 2010, the Union of Concerned Scientists (UAS) claimed that the CDC Advisory Committee on Childhood Lead Poisoning had been expected to lower the action level for lead in drinking water below 10 micrograms per deciliter in the summer of 2002.[64] According to the UAS, Tommy Thompson, the Secretary of Health and Human Services, took the unprecedented step of rejecting a number of nominees to the committee selected by staff scientists.[64] Instead, the group claims, Thompson appointed at least two appointees with financial ties to the lead industry.[64] A 2010 Washington Post editorial cited the group's statement as a reason why the District's lead contamination "was practically inevitable" due to politicization of the CDC.[65]

Eleanor Holmes Norton, a Delegate to Congress representing the District, accused the CDC of a coverup.[61] Jim Graham, a member of the DC Council, said "To now learn that the Centers for Disease Control not only got it wrong but may have intentionally misled District residents and our water agency is the ultimate betrayal of the public trust".[61]

Lead service replacement continued through the 2000s (decade), but may not have helped the problem.

A 2010 study by Brown at the CDC essentially confirmed Edwards's findings.[66] It also found that the 15,000 "partial pipe replacements" performed by WASA—where lead service lines were replaced up to a homeowner's property line, but no further—may not have effectively reduced lead levels, and may have made the problem worse.[67] WASA spent $97 million to replace 17,000 pipes, including the 15,000 partial replacements.[68] A Post article about the report lead to jammed phone lines at WASA and increased demand for bottled-water delivery.[67] The study indicated that there is no safe level of lead in drinking water, and that children in homes with even a partial lead service line are at a much higher risk of lead poisoning than those with no lead in the line.[69] WASA said the finding "is not news" to them; General Manager George Hawkins told WAMU that the utility had been acting as if the CDC's findings were fact for some time before the report was released.[70] Hawkins said that WAMU was not seeing elevated levels of lead in homes with partial pipe replacements.[70]

John Parkhurst, et al. lawsuit

On February 17, 2009, John Parkhurst, the father of twin boys living on Capitol Hill, through his attorneys Stefanie Roemer and David Sanford of Sanford, Wittels & Heisler, filed a class action lawsuit against WASA in the Superior Court of the District of Columbia, seeking $200 million in compensatory damages plus punitive damages.[71] Parkhurst, a 50-year-old single father and psychologist, prepared food and formula for the boys using tap water from the time they were 8 months old until 2002, when they were two years old.[72] The complaint was later amended to add additional five children, on behalf of a proposed class consisting of all children who, at any time from 2000 to 2004, while six years of age or younger, consumed water supplied by WASA that passed through a line containing lead (whether directly or prenatally through their birth mothers), and who had blood-lead levels of 10μg/dl or higher. The suit claims that WASA "undertook Herculean efforts to shield itself from liability and to otherwise deny responsibility".[71] Contemporary news reports indicated that WASA had not seen the lawsuit at the time the story broke, but included comments from WASA spokespeople that more studies would be needed before lead in drinking water could be linked to health and behavioral issues.[73] The agency said that such claims would need to be substantiated on a case-by-case basis.[71] WASA's motion to dismiss the complaint was denied in October 2009.[74] In 2012 the named plaintiffs on the case sought to make the case a class action, but on April 8, 2013, judge Anthony C. Epstein denied their motion for class certification stating that the "class of tap water drinkers under 7 years old with elevated blood lead levels was too broad", and that it was not clear the class had or even possibly would suffer any injury.[75]

See also

References

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 3.3 3.4 Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 5.3 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 7.3 7.4 7.5 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 8.3 8.4 8.5 8.6 Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 9.2 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.00 10.01 10.02 10.03 10.04 10.05 10.06 10.07 10.08 10.09 10.10 10.11 10.12 10.13 10.14 10.15 Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 11.2 Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 14.2 Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 16.2 16.3 16.4 16.5 16.6 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 18.2 Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. 20.0 20.1 20.2 Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. "Blood Lead Levels in Residents of Homes with Elevated Lead in Tap Water --- District of Columbia, 2004" (MMWR, April 2, 2004)
  24. 24.0 24.1 24.2 24.3 24.4 24.5 24.6 Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 25.2 25.3 Lua error in package.lua at line 80: module 'strict' not found.
  26. 26.0 26.1 Lua error in package.lua at line 80: module 'strict' not found.
  27. 27.0 27.1 27.2 Lua error in package.lua at line 80: module 'strict' not found.
  28. 28.0 28.1 28.2 28.3 28.4 Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. 30.0 30.1 30.2 30.3 30.4 30.5 Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. 32.0 32.1 Lua error in package.lua at line 80: module 'strict' not found.
  33. 33.0 33.1 Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. 39.0 39.1 39.2 39.3 Lua error in package.lua at line 80: module 'strict' not found.
  40. 40.0 40.1 40.2 40.3 Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. 42.0 42.1 42.2 Lua error in package.lua at line 80: module 'strict' not found.
  43. 43.0 43.1 Lua error in package.lua at line 80: module 'strict' not found.
  44. 44.0 44.1 Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. 46.0 46.1 Lua error in package.lua at line 80: module 'strict' not found.
  47. 47.0 47.1 Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. 50.0 50.1 50.2 50.3 Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. 52.0 52.1 52.2 Lua error in package.lua at line 80: module 'strict' not found.
  53. 53.0 53.1 53.2 53.3 Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. 56.0 56.1 56.2 56.3 56.4 Lua error in package.lua at line 80: module 'strict' not found.
  57. 57.0 57.1 57.2 57.3 Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. 59.0 59.1 59.2 59.3 59.4 59.5 Lua error in package.lua at line 80: module 'strict' not found.
  60. 60.0 60.1 60.2 60.3 60.4 60.5 Lua error in package.lua at line 80: module 'strict' not found.
  61. 61.0 61.1 61.2 61.3 61.4 Lua error in package.lua at line 80: module 'strict' not found.
  62. 62.0 62.1 Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. 64.0 64.1 64.2 Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. 67.0 67.1 Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. 70.0 70.1 Lua error in package.lua at line 80: module 'strict' not found.
  71. 71.0 71.1 71.2 Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.