Non-Invasive Determination of DNAPL Source Zone Configuration

 

Submitted by:

Project Sponsor

Sara Sayler

OC-ALC/EMPE

sara.sayler@tinker.af.mil

405-734-4580

Technical Thrust Area Lead

Name

Organization

E-mail address

Phone Number

                                                               

1.0      Background. 1

2.0      Problem Statement 1

3.0      Anticipated Methodology/Tasks. 1

4.0      Anticipated Schedule. 1

5.0      Anticipated Deliverables. 2

6.0      Anticipated Benefits. 2

 

 

1.0    Background

Many contaminated groundwater sites on Tinker Air Force Base contain chlorinated solvents such as trichloroethene (TCE) and perchloroethene (PCE). There are many remediation technologies available for these types of contaminants, however, no remediation will be successful until the source of the contaminant plume is delineated.  The purpose of this project will be to develop a methodology with which to delineate possible source zone configurations (ie point source or multiple sources, is the dissolved plume near the source or far down-gradient, how far from the source has the dissolved phase traveled).  The greater the knowledge of the contaminant plume source, the more the remediation costs can be minimized.

 

2.0    Problem Statement

Develop a non-invasive method for determining DNAPL source zone configurations in the sub-surface.

3.0    Anticipated Methodology/Tasks

 

  1. Develop a methodology with which to delineate possible source zone configurations.
  2. Submit a final report which includes the results as well as a description of any work associated with the project.
  3. Submit brief monthly status updates to the project manager for the purpose of project tracking.

 

4.0    Anticipated Schedule

For the 2003 CASI program, the following schedules/periods of performance are allowed (you may wish to include this list and check all of the periods of performance that you would accept, i.e.,):

[X] Execution and Completion of Project between June 1 and August 31, 2003.

[  ] Execution and Completion of Project between June 1 and May 31, 2004

[  ] Executed as a single project, or

[  ] Executed in two or more phases with an intermediate set of deliverables and successful completion of the intermediate deliverables required before funding successive phase(s).  NOTE: CASI research phases will normally have completion dates that correspond to the academic researcher’s semester schedule, i.e., August 15 or December 31.

[  ] Execution and Completion of Project between August 15, 2003 and May 31, 2004

[  ] Executed as a single project, or

[  ] Executed in two or more phases with an intermediate set of deliverables and successful completion of the intermediate deliverables required before funding successive phase(s).  NOTE: CASI research phases will normally have completion dates that correspond to the academic researcher’s semester schedule, i.e., August 15 or December 31.

[  ]  Execution as the first phase of a multi-year project.  NOTE: Due to funding mechanisms, only the effort between June 1, 2003 and May 31, 2004 can be funded by the 2003 CASI program.  The project must produce a set of intermediate deliverables at the end of the 2003 funding cycle and funding of successive phases/years is contingent upon funding availability, project priority, and performance.

5.0    Anticipated Deliverables

A Final Report shall be submitted which includes the results as well as a description of any work associated with the project.  A cost benefit analysis will be required and a final briefing will be held at the end of the project period.  In addition, brief monthly status updates shall be submitted to the project manager for the purpose of project tracking.

6.0    Anticipated Benefits