<?xml version="1.0" encoding="UTF-8"?>

<ns1:descriptiveReport xmlns:ns1="http://Pydro.com/2014/02/DescriptiveReport" xmlns:ns2="http://Pydro.com/2014/02/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<ns1:metadata>
		<ns1:projectMetadata>
			<ns2:number>OPR-K370-KR-15</ns2:number>
			<ns2:name>Port Mansfield, TX</ns2:name>
			<ns2:generalLocality>Port Mansfield, TX</ns2:generalLocality>
			<ns2:fieldUnit>eTrac Inc. </ns2:fieldUnit>
		</ns1:projectMetadata>
		<ns1:registryMetadata>
			<ns2:registryNumber>H12761</ns2:registryNumber>
			<ns2:sheetID>1</ns2:sheetID>
			<ns2:registryInstructions xsi:nil="true"/>

			<ns2:sublocality>Approaches to Port Mansfield </ns2:sublocality>
			<ns2:stateOrTerritory>Texas </ns2:stateOrTerritory>
			<ns2:country>United States</ns2:country>
			<ns2:scale>40000</ns2:scale>
		</ns1:registryMetadata>
		<ns1:surveyMetadata>
			<ns2:year>2015</ns2:year>
			<ns2:chiefOfParty>David Neff, ACSM C.H. </ns2:chiefOfParty>
			<ns2:projectType>Basic Hydrographic Survey</ns2:projectType>
			<ns2:PIDate>2015-06-23</ns2:PIDate>
			<ns2:datesOfSurvey>
				<ns2:start>2015-06-05</ns2:start>
				<ns2:end>2015-08-11</ns2:end>
			</ns2:datesOfSurvey>
			<ns2:equipmentTypes>
				<ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment>
				<ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment>
				<ns2:imageryEquipment></ns2:imageryEquipment>
			</ns2:equipmentTypes>
			<ns2:acquisition>
				<ns2:units>meters</ns2:units>
			</ns2:acquisition>
			<ns2:horizontalCoordinateSystem>Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem>
			<ns2:timeZone>UTC</ns2:timeZone>
			<ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier>
			<ns2:titlesheetRemarks>
				<ns2:fieldRemarks>All times are UTC. The purpose of this survey is to update existing NOS nautical charts. H12761 will cover approximately  27 square nautical miles of survey area in  the Approaches to Port Mansfield as designated in NOAA Hydrographic Survey Priorities, 2012 edition. SUBCONSULTANT: Geodynamics LLC, 310A Greenfield Dr., Newport, NC 98570 SUBCONSULTANT: Theory Marine, 777 Viewcrest DR., Ventura, CA 93003 Projections: UTM 14N, NAD 83</ns2:fieldRemarks>
				<ns2:branchRemarks xsi:nil="true"/>

			</ns2:titlesheetRemarks>
		</ns1:surveyMetadata>
		<ns1:assignment>Contractor</ns1:assignment>
	</ns1:metadata>
	<ns1:areaSurveyed>
		<ns1:areaDescription>
			<ns2:discussion>eTrac Inc. conducted hydrographic survey operations in the vicinity of Port Mansfield, TX. H12761 covers approximately 27 square nautical miles of survey area, including the safety fairway approaching Port Mansfield and part of the entrance channel to Port Mansfield, TX. H12761 is generally rectangular in geometry, and is approximately 8 nautical miles wide (E-W) by 3 nautical miles long (N-S).  

Survey was conducted within these limits between June 5, 2015 (DN156) and August 11, 2015 (DN223). </ns2:discussion>
			<ns2:limits>
				<ns2:northWest>
					<ns2:latitude hemisphere="N">26.598591</ns2:latitude>
					<ns2:longitude hemisphere="W">97.289111</ns2:longitude>
				</ns2:northWest>
				<ns2:southEast>
					<ns2:latitude hemisphere="N">26.555019</ns2:latitude>
					<ns2:longitude hemisphere="W">97.115995</ns2:longitude>
				</ns2:southEast>
			</ns2:limits>
			<ns2:images>
				<ns2:caption>Survey Limits (Black dashed line)</ns2:caption>
				<ns2:link>SUPPORTFILES/H12761_SURVEYLIMITS.PNG</ns2:link>
			</ns2:images>
			<ns2:comments/>
		</ns1:areaDescription>
		<ns1:surveyLimits>
			<ns2:results deviation="true">
				<ns2:discussion>All data were acquired in accordance with the requirements in the Project Instructions and specifications set forth in the Hydrographic Survey Specifications and Deliverables 2015 Edition (HSSD 2015). </ns2:discussion>
			</ns2:results>
			<ns2:comments/>
		</ns1:surveyLimits>
		<ns1:surveyPurpose>
			<ns2:discussion>The purpose of this survey is to update existing NOS nautical charts. H12761 covers approximately 27 square nautical miles of survey area in Port Mansfield, TX as designated in NOAA Hydrographic Survey Priorities, 2012 edition. </ns2:discussion>
			<ns2:comments/>
		</ns1:surveyPurpose>
		<ns1:surveyQuality>
			<ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy>
			<ns2:discussion>Survey H12761 is accurate to IHO Order 1a as required per the HSSD 2015.</ns2:discussion>
			<ns2:comments/>
		</ns1:surveyQuality>
		<ns1:surveyCoverage>
			<ns2:results deviation="true">
				<ns2:discussion>Survey Coverage was in accordance with the requirements in the Project Instructions and HSSD 2015.  H12761 was surveyed to 100% SSS with concurrent set line spacing MBES with backscatter standards set forth in the HSSD 2015. The survey area inside the Port Mansfield Channel and around the entrance jetties was surveyed to complete MBES with backscatter standards set forth in HSSD 2015 where possible. Figure 3 details the area covered inshore of the NALL and inside the entrance channel. Multiple holidays are present, however coverage in this area was deemed acceptable through correspondence with the COTR. Reference Email Correspondence in Appendix II of this report. </ns2:discussion>
				<ns2:images>
					<ns2:caption>Survey Coverage</ns2:caption>
					<ns2:link>SUPPORTFILES/H12761_SURVEY_COVERAGE.PNG</ns2:link>
				</ns2:images>
				<ns2:images>
					<ns2:caption>Entrance Channel Survey Coverage</ns2:caption>
					<ns2:link>SUPPORTFILES/H12761_CHANNEL_SURVEY_COVERAGE.PNG</ns2:link>
				</ns2:images>
			</ns2:results>
			<ns2:comments/>
		</ns1:surveyCoverage>
		<ns1:surveyStatistics>
			<ns2:LNM>
				<ns2:vesselLNM>
					<ns2:vessel>
						<ns2:hullID>JAB</ns2:hullID>
						<ns2:statistics>
							<ns2:MS_SBES>0</ns2:MS_SBES>
							<ns2:MS_MBES>8</ns2:MS_MBES>
							<ns2:MS_lidar>0</ns2:MS_lidar>
							<ns2:MS_SSS>0</ns2:MS_SSS>
							<ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES>
							<ns2:MS_MBES_SSS>616</ns2:MS_MBES_SSS>
							<ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS>
							<ns2:XL_MBES_SBES>48</ns2:XL_MBES_SBES>
							<ns2:XL_lidar>0</ns2:XL_lidar>
						</ns2:statistics>
					</ns2:vessel>
					<ns2:vessel>
						<ns2:hullID>Benthos</ns2:hullID>
						<ns2:statistics>
							<ns2:MS_SBES>0</ns2:MS_SBES>
							<ns2:MS_MBES>7</ns2:MS_MBES>
							<ns2:MS_lidar>0</ns2:MS_lidar>
							<ns2:MS_SSS>0</ns2:MS_SSS>
							<ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES>
							<ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS>
							<ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS>
							<ns2:XL_MBES_SBES>8</ns2:XL_MBES_SBES>
							<ns2:XL_lidar>0</ns2:XL_lidar>
						</ns2:statistics>
					</ns2:vessel>
					<ns2:vessel>
						<ns2:hullID>Taku</ns2:hullID>
						<ns2:statistics>
							<ns2:MS_SBES>0</ns2:MS_SBES>
							<ns2:MS_MBES>7</ns2:MS_MBES>
							<ns2:MS_lidar>0</ns2:MS_lidar>
							<ns2:MS_SSS>0</ns2:MS_SSS>
							<ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES>
							<ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS>
							<ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS>
							<ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES>
							<ns2:XL_lidar>0</ns2:XL_lidar>
						</ns2:statistics>
					</ns2:vessel>
				</ns2:vesselLNM>
				<ns2:totalLNM>
					<ns2:MS_SBES>0</ns2:MS_SBES>
					<ns2:MS_MBES>0</ns2:MS_MBES>
					<ns2:MS_lidar>0</ns2:MS_lidar>
					<ns2:MS_SSS>0</ns2:MS_SSS>
					<ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES>
					<ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS>
					<ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS>
					<ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES>
					<ns2:XL_lidar>0</ns2:XL_lidar>
					<ns2:percentXLLNM>0</ns2:percentXLLNM>
				</ns2:totalLNM>
			</ns2:LNM>
			<ns2:totalSurveyStats>
				<ns2:bottomSamples>5</ns2:bottomSamples>
				<ns2:AWOIS>0</ns2:AWOIS>
				<ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints>
				<ns2:DP>0</ns2:DP>
				<ns2:diveOps>0</ns2:diveOps>
				<ns2:SNM>27</ns2:SNM>
			</ns2:totalSurveyStats>
			<ns2:surveyDates>2015-06-05</ns2:surveyDates>
			<ns2:surveyDates>2015-06-06</ns2:surveyDates>
			<ns2:surveyDates>2015-06-07</ns2:surveyDates>
			<ns2:surveyDates>2015-06-08</ns2:surveyDates>
			<ns2:surveyDates>2015-06-09</ns2:surveyDates>
			<ns2:surveyDates>2015-06-10</ns2:surveyDates>
			<ns2:surveyDates>2015-06-11</ns2:surveyDates>
			<ns2:surveyDates>2015-06-12</ns2:surveyDates>
			<ns2:surveyDates>2015-06-19</ns2:surveyDates>
			<ns2:surveyDates>2015-06-20</ns2:surveyDates>
			<ns2:surveyDates>2015-06-22</ns2:surveyDates>
			<ns2:surveyDates>2015-06-26</ns2:surveyDates>
			<ns2:surveyDates>2015-06-27</ns2:surveyDates>
			<ns2:surveyDates>2015-06-28</ns2:surveyDates>
			<ns2:surveyDates>2015-06-29</ns2:surveyDates>
			<ns2:surveyDates>2015-07-02</ns2:surveyDates>
			<ns2:surveyDates>2015-07-03</ns2:surveyDates>
			<ns2:surveyDates>2015-07-05</ns2:surveyDates>
			<ns2:surveyDates>2015-07-11</ns2:surveyDates>
			<ns2:surveyDates>2015-07-12</ns2:surveyDates>
			<ns2:surveyDates>2015-07-13</ns2:surveyDates>
			<ns2:surveyDates>2015-07-13</ns2:surveyDates>
			<ns2:surveyDates>2015-07-29</ns2:surveyDates>
			<ns2:surveyDates>2015-08-03</ns2:surveyDates>
			<ns2:surveyDates>2015-08-04</ns2:surveyDates>
			<ns2:surveyDates>2015-08-08</ns2:surveyDates>
			<ns2:surveyDates>2015-08-09</ns2:surveyDates>
			<ns2:surveyDates>2015-08-10</ns2:surveyDates>
			<ns2:surveyDates>2015-08-11</ns2:surveyDates>
			<ns2:discussion xsi:nil="true"/>

			<ns2:comments/>
		</ns1:surveyStatistics>
	</ns1:areaSurveyed>
	<ns1:dataAcquisitionAndProcessing>
		<ns1:equipmentAndVessels>
			<ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data are discussed in the following sections.</ns1:discussion>
			<ns1:vessels>
				<ns1:vessel>
					<ns2:hullID>M/V Jab</ns2:hullID>
					<ns2:LOA units="meters">13</ns2:LOA>
					<ns2:draft units="meters">0.75</ns2:draft>
				</ns1:vessel>
				<ns1:vessel>
					<ns2:hullID>R/V Benthos</ns2:hullID>
					<ns2:LOA units="meters">10</ns2:LOA>
					<ns2:draft units="meters">0.6</ns2:draft>
				</ns1:vessel>
				<ns1:vessel>
					<ns2:hullID>R/V Taku</ns2:hullID>
					<ns2:LOA units="meters">10</ns2:LOA>
					<ns2:draft units="meters">0.6</ns2:draft>
				</ns1:vessel>
				<ns1:discussion>The M/V Jab is a 13 meter aluminum catamaran equipped with a multibeam moonpool and an A-frame for towed body operations.

The R/V Benthos is a 10 meter aluminum catamaran equipped with a custom over-the-side (port) multibeam hydraulic pole mount, as well as an A-Frame for towed body operations.

The R/V Taku is a 10 meter aluminum catamaran equipped with an Universal Sonar Mount (USM) over-the-side (starboard) multibeam mount, as well as an A-Frame for towed body operations. 
</ns1:discussion>
				<ns1:comments/>
			</ns1:vessels>
			<ns1:equipment>
				<ns1:majorSystem>
					<ns2:manufacturer>R2Sonic</ns2:manufacturer>
					<ns2:model>2024</ns2:model>
					<ns2:type>MBES</ns2:type>
				</ns1:majorSystem>
				<ns1:majorSystem>
					<ns2:manufacturer>Applanix</ns2:manufacturer>
					<ns2:model>POSMV 320 V5</ns2:model>
					<ns2:type>Positioning and Attitude System</ns2:type>
				</ns1:majorSystem>
				<ns1:majorSystem>
					<ns2:manufacturer>AML</ns2:manufacturer>
					<ns2:model>Base.X</ns2:model>
					<ns2:type>Sound Speed System</ns2:type>
				</ns1:majorSystem>
				<ns1:majorSystem>
					<ns2:manufacturer>AML</ns2:manufacturer>
					<ns2:model>Minos.X</ns2:model>
					<ns2:type>Sound Speed System</ns2:type>
				</ns1:majorSystem>
				<ns1:majorSystem>
					<ns2:manufacturer>Trimble</ns2:manufacturer>
					<ns2:model>SPS461</ns2:model>
					<ns2:type>Positioning System</ns2:type>
				</ns1:majorSystem>
				<ns1:majorSystem>
					<ns2:manufacturer>Trimble</ns2:manufacturer>
					<ns2:model>DSM232</ns2:model>
					<ns2:type>Positioning System</ns2:type>
				</ns1:majorSystem>
				<ns1:majorSystem>
					<ns2:manufacturer>Edgetech</ns2:manufacturer>
					<ns2:model>4200</ns2:model>
					<ns2:type>SSS</ns2:type>
				</ns1:majorSystem>
				<ns1:discussion>Note: The major systems listed above were used on each vessel. The AML Minos.X, AML Base.X, Trimble DSM232 and Edgetech 4200 Sidescan Sonar were utilized on  the M/V Jab. R/V Benthos utilized an AML Base.X and Trimble SPS461. R/V Taku utilized an AML Base.X and Trimble DSM232. </ns1:discussion>
				<ns1:comments/>
			</ns1:equipment>
			<ns1:comments/>
		</ns1:equipmentAndVessels>
		<ns1:qualityControl>
			<ns1:crosslines>
				<ns2:discussion>A comparison of crossline mileage to mainscheme mileage yields a crossline percentage of 8.85%, and is noted to be above the required 8%. 

A beam-by-beam statistical analysis was performed using the Line QC reporting tool in Caris HIPS and SIPS 9.0. A 1 meter CUBE weighted BASE surface was created incorporating only the mainscheme lines and excluded crosslines. Note: this surface was created for QC only and is not submitted as a surface deliverable. The Line QC reporting tool was used to perform the beam-by-beam comparison of the crossline data to the mainscheme surface. Comparisons showed excellent agreement, well above 95% of the allowable TVU. Note: the statistical analysis excluded the outer 5 beams (beams 1-5 and beams 252-256), as these beams were excluded from both mainsheme and crossline data across the entire project. 

The beam-to-beam crossline comparison report generated through the Caris QC Reporting tool is included in Separate II. 

Below is a graph of crossline comparison statistics showing IHO Special Order and Order 1a compliance per beam. </ns2:discussion>
				<ns2:images>
					<ns2:caption>H12761 Crossline Comparison</ns2:caption>
					<ns2:link>SUPPORTFILES/H12761_CROSSLINES.PNG</ns2:link>
				</ns2:images>
				<ns2:comments/>
			</ns1:crosslines>
			<ns1:uncertainty>
				<ns2:values>
					<ns2:tideUncertainty>
						<ns2:measured units="meters">0.22</ns2:measured>
						<ns2:zoning units="meters">0</ns2:zoning>
					</ns2:tideUncertainty>
					<ns2:soundSpeedUncertainty>
						<ns2:hullID>M/V Jab</ns2:hullID>
						<ns2:measuredCTD units="meters/second">4</ns2:measuredCTD>
						<ns2:measuredMVP units="meters/second">0</ns2:measuredMVP>
						<ns2:surface units="meters/second">2</ns2:surface>
					</ns2:soundSpeedUncertainty>
					<ns2:soundSpeedUncertainty>
						<ns2:hullID>R/V Benthos</ns2:hullID>
						<ns2:measuredCTD units="meters/second">4</ns2:measuredCTD>
						<ns2:measuredMVP units="meters/second">0</ns2:measuredMVP>
						<ns2:surface units="meters/second">2</ns2:surface>
					</ns2:soundSpeedUncertainty>
					<ns2:soundSpeedUncertainty>
						<ns2:hullID>R/V Taku </ns2:hullID>
						<ns2:measuredCTD units="meters/second">4</ns2:measuredCTD>
						<ns2:measuredMVP units="meters/second">0</ns2:measuredMVP>
						<ns2:surface units="meters/second">2</ns2:surface>
					</ns2:soundSpeedUncertainty>
				</ns2:values>
				<ns2:discussion>Note: Tide TPU value given as 2 sigma. 

Standard deviation and uncertainty BASE surfaces were utilized during data processing to search for features, water column noise, and systematic errors. 

A custom layer was created within the BASE surface utilizing the Deep and Shoal layers in the following configuration:

Custom Layer = (Deep - Shoal)^2

By viewing this custom layer, seafloor features, water column noise, and systematic errors are graphically exaggerated and can easily be identified for further examination. 

A TVU QC layer was created within the BASE surface utilizing the Uncertainty and Depth layers in the following configuration:

-Uncertainty/((0.5^2 +((Depth*0.013)^2))^0.5)

By viewing the TVU QC layer, nodes that exceed the IHO Order 1a uncertainty standards can be identified and further analyzed.  
  
Standard deviation and uncertainty were quantified using the QC Reporting tool within Caris HIPS and SIPS 9.0. The option "Greater of the two" was selected in the reporting tool in order to generate statistics quantifying the maximum error occurring within the data. IHO Order 1a uncertainty specification was met by 100% of the nodes.</ns2:discussion>
				<ns2:comments/>
			</ns1:uncertainty>
			<ns1:junctions>
				<ns2:discussion/>
				<ns2:junction>
					<ns2:survey>
						<ns2:registryNumber>H12762</ns2:registryNumber>
						<ns2:scale>40000</ns2:scale>
						<ns2:year>2015</ns2:year>
						<ns2:fieldUnit>eTrac Inc. </ns2:fieldUnit>
						<ns2:relativeLocation>E</ns2:relativeLocation>
					</ns2:survey>
					<ns2:discussion>H12761 junctions with H12762 to the east. The junction comparison was performed using approximately 250m of overlapping data between H12761 and H12762. Depths were compared in Caris HIPS and SIPS 9.0 by creating a 2 meter difference surface between the junctioning datasets. Note: the 2 meter difference surface was created for comparison efforts only and is not submitted as a surface deliverable. The comparison showed excellent agreement between H12761 and H12762. Depth differences generally were within 30cm or less, with a majority of depth differences being less than 10 cm. Junction comparison statistics are included in Separate II.</ns2:discussion>
					<ns2:images>
						<ns2:caption>Juction Comparison (H12761 to H12762)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_H12762_2M_DIFFERENCE.PNG</ns2:link>
					</ns2:images>
					<ns2:comments/>
				</ns2:junction>
				<ns2:comments/>
			</ns1:junctions>
			<ns1:sonarQCChecks>
				<ns2:results deviation="false">
					<ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:sonarQCChecks>
			<ns1:equipmentEffectiveness>
				<ns2:results deviation="false">
					<ns2:issue>
						<ns2:title>None Exist</ns2:title>
						<ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion>
						<ns2:comments/>
					</ns2:issue>
				</ns2:results>
				<ns2:comments/>
			</ns1:equipmentEffectiveness>
			<ns1:factorsAffectingSoundings>
				<ns2:results deviation="false">
					<ns2:issue>
						<ns2:title>None Exist</ns2:title>
						<ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion>
						<ns2:comments/>
					</ns2:issue>
				</ns2:results>
				<ns2:comments/>
			</ns1:factorsAffectingSoundings>
			<ns1:soundSpeedMethods>
				<ns1:castFrequency>SVP casts were generally taken every 2 hours. Ocassionally casts would exceed a 2 hour frequency, however would never exceed a 4 hour frequency. Casts were applied in QPS QINSy acquisition software at the time of the cast. Surface SVP measured at 1Hz was compared to surface speed from the current profile in realtime. If the surface velocity comparison was in excess of 2m/s at any time during survey operations, a new cast was taken.
 
</ns1:castFrequency>
				<ns1:discussion>SVP surface velocities were compared in realtime and profile to profile for each cast on the vessel. Additionally, profiles were compared day-to-day in the field office using the SVPTrac program, developed in-house by eTrac Inc., to better understand trends for efficient acquisition planning. </ns1:discussion>
				<ns1:images>
					<ns2:caption>Example of Daily SVP Data Plot (DN159)</ns2:caption>
					<ns2:link>SUPPORTFILES/H12761_DAILYSVPTRAC.JPG</ns2:link>
				</ns1:images>
				<ns1:images>
					<ns2:caption>Example of Day to Day SVP Comparison (DN159 and DN160)</ns2:caption>
					<ns2:link>SUPPORTFILES/H12761_DAYTODAYSVPTRAC.JPG</ns2:link>
				</ns1:images>
				<ns1:comments/>
			</ns1:soundSpeedMethods>
			<ns1:coverageEquipmentAndMethods>
				<ns2:results deviation="false">
					<ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:coverageEquipmentAndMethods>
			<ns1:additionalQualityControl>
				<ns2:issue>
					<ns2:title>Data Density Evaluation</ns2:title>
					<ns2:discussion>In order to determine if the density of the data met the specified 5 soundings per node, data density was evaluated using the DensityTrac program, developed in-house by eTrac Inc. Each BASE surface's nodes were exported to an ASCII CSV file where the fields were (Easting, Northing, Denisty) for each node. The CSV file was then loaded into the DensityTrac program and density statistics were computed. For H12761 the following percentages represent the results of the density testing:

Concurrent MBES/SSS ( 1m CUBE weighted BASE Surface ) = 98.09% of nodes are composed from at least 5 soundings. 

Concurrent MBES/SSS ( 2m CUBE weighted BASE Surface ) = 99.12% of nodes are composed from at least 5 soundings. </ns2:discussion>
					<ns2:images>
						<ns2:caption>H12761 1m MBES/SSS Density Distribution Statistics</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_MB_1M_MLLW_DENSITY.PNG</ns2:link>
					</ns2:images>
					<ns2:images>
						<ns2:caption>H12761 2m MBES/SSS Density Distribution Statistics</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_MB_2M_MLLW_DENSITY.PNG</ns2:link>
					</ns2:images>
					<ns2:comments/>
				</ns2:issue>
				<ns2:comments/>
			</ns1:additionalQualityControl>
		</ns1:qualityControl>
		<ns1:echoSoundingCorrections>
			<ns1:corrections>
				<ns2:results deviation="false">
					<ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:corrections>
			<ns1:calibrations>
				<ns2:results deviation="false">
					<ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion>
					<ns2:calibration xsi:nil="true"/>

				</ns2:results>
				<ns2:comments/>
			</ns1:calibrations>
			<ns1:additionalIssues>
				<ns2:comments/>
			</ns1:additionalIssues>
		</ns1:echoSoundingCorrections>
		<ns1:backscatter>
			<ns2:results acquired="true">
				<ns2:discussion>Backscatter data were collected throughout the survey and are retained in the raw XTF files. Every effort was made in the field to collect quality backscatter data while maintaining the primary mandate of high quality bathymetric data. While no processing or analysis of backscatter was required, eTrac Inc. engaged in a minimal effort to verify coverage and general quality of the backscatter data collected. Raw backscatter data were viewed in Caris HIPS and SIPS 9.0  to ensure collection criteria had been met. Shown below is an example of the unprocessed backscatter mosaic from H12761 DN163.</ns2:discussion>
				<ns2:images>
					<ns2:caption>Raw Backscatter From M/V Jab (DN163)</ns2:caption>
					<ns2:link>SUPPORTFILES/H12761_DN163_BACKSCATTER.PNG</ns2:link>
				</ns2:images>
			</ns2:results>
			<ns2:comments/>
		</ns1:backscatter>
		<ns1:dataProcessing>
			<ns1:softwareUpdates>
				<ns1:featureObjectCatalog>NOAA Profile V_5_3_2</ns1:featureObjectCatalog>
				<ns1:discussion xsi:nil="true"/>

				<ns1:comments/>
			</ns1:softwareUpdates>
			<ns1:surfaces>
				<ns1:surface>
					<ns2:surfaceName>H12761_MB_ 1m_MLLW</ns2:surfaceName>
					<ns2:surfaceType>CUBE</ns2:surfaceType>
					<ns2:resolution units="meters">1</ns2:resolution>
					<ns2:depthRange>
						<ns2:min units="meters">1.42</ns2:min>
						<ns2:max units="meters">20</ns2:max>
					</ns2:depthRange>
					<ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter>
					<ns2:purpose>Complete MBES</ns2:purpose>
				</ns1:surface>
				<ns1:surface>
					<ns2:surfaceName>H12761_MB_2m_MLLW</ns2:surfaceName>
					<ns2:surfaceType>CUBE</ns2:surfaceType>
					<ns2:resolution units="meters">2</ns2:resolution>
					<ns2:depthRange>
						<ns2:min units="meters">18</ns2:min>
						<ns2:max units="meters">24.42</ns2:max>
					</ns2:depthRange>
					<ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter>
					<ns2:purpose>Complete MBES</ns2:purpose>
				</ns1:surface>
				<ns1:surface>
					<ns2:surfaceName>H12761_MB_1m_Parent</ns2:surfaceName>
					<ns2:surfaceType>CUBE</ns2:surfaceType>
					<ns2:resolution units="meters">1</ns2:resolution>
					<ns2:depthRange>
						<ns2:min units="meters">1.42</ns2:min>
						<ns2:max units="meters">24.42</ns2:max>
					</ns2:depthRange>
					<ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter>
					<ns2:purpose>Complete MBES</ns2:purpose>
				</ns1:surface>
				<ns1:surface>
					<ns2:surfaceName>H12761_MB_2m_Parent</ns2:surfaceName>
					<ns2:surfaceType>CUBE</ns2:surfaceType>
					<ns2:resolution units="meters">2</ns2:resolution>
					<ns2:depthRange>
						<ns2:min units="meters">1.43</ns2:min>
						<ns2:max units="meters">24.42</ns2:max>
					</ns2:depthRange>
					<ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter>
					<ns2:purpose>Complete MBES</ns2:purpose>
				</ns1:surface>
				<ns1:surface>
					<ns2:surfaceName>H12761_SSS_1m_100Percent_Mosaic</ns2:surfaceName>
					<ns2:surfaceType>SSS Mosaic</ns2:surfaceType>
					<ns2:resolution units="meters">1</ns2:resolution>
					<ns2:depthRange>
						<ns2:min units="meters">0</ns2:min>
						<ns2:max units="meters">0</ns2:max>
					</ns2:depthRange>
					<ns2:surfaceParameter>N/A</ns2:surfaceParameter>
					<ns2:purpose>100% SSS</ns2:purpose>
				</ns1:surface>
				<ns1:surface>
					<ns2:surfaceName>H12761_SSS_1m_200Perecnt_Mosaic</ns2:surfaceName>
					<ns2:surfaceType>SSS Mosaic</ns2:surfaceType>
					<ns2:resolution units="meters">1</ns2:resolution>
					<ns2:depthRange>
						<ns2:min units="meters">0</ns2:min>
						<ns2:max units="meters">0</ns2:max>
					</ns2:depthRange>
					<ns2:surfaceParameter>N/A</ns2:surfaceParameter>
					<ns2:purpose>200% SSS</ns2:purpose>
				</ns1:surface>
				<ns1:discussion>In areas shoaler than 20 meters, a 1 meter surface is provided meeting 100% SSS with concurrent set line spacing MBES with backscatter specifications.

In areas deeper than 18 meters, a 2 meter surface is provided meeting 100% SSS with concurrent set line spacing MBES with backscatter specifications. 

Parent surfaces of the 1 meter and 2 meter surfaces are provided, both covering the entire survey area of H12761.   

A sidescan sonar mosaic is provided for the 100% SSS survey performed.

A sidescan sonar mosaic is provided for the 200% SSS survey performed. Note: The 200% SSS survey includes 2 areas, each covering a 100 meter radius circle for the purpose of feature disproval. </ns1:discussion>
				<ns1:images>
					<ns2:caption>H12761 Delivered BASE Surface Coverage Graphic</ns2:caption>
					<ns2:link>SUPPORTFILES/H12761_SURFACES_COVERAGE.PNG</ns2:link>
				</ns1:images>
				<ns1:comments/>
			</ns1:surfaces>
			<ns1:additionalDataProcessing>
				<ns2:comments/>
			</ns1:additionalDataProcessing>
		</ns1:dataProcessing>
	</ns1:dataAcquisitionAndProcessing>
	<ns1:verticalAndHorizontalControl>
		<ns1:discussion>
</ns1:discussion>
		<ns1:verticalControl>
			<ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum>
			<ns2:standard_or_ERZT used="true">
				<ns2:methodsUsed>Discrete Zoning</ns2:methodsUsed>
				<ns2:tideStations>
					<ns2:NWLONGauges>
						<ns2:stationName>Corpus Christi TX</ns2:stationName>
						<ns2:stationID>877-5870</ns2:stationID>
					</ns2:NWLONGauges>
				</ns2:tideStations>
				<ns2:correctorFiles>
					<ns2:waterLevels>
						<ns2:fileName>8775870.tid</ns2:fileName>
						<ns2:status>Verified Observed</ns2:status>
					</ns2:waterLevels>
					<ns2:tideCorrectors>
						<ns2:fileName>K370KR2015CORP.zdf</ns2:fileName>
						<ns2:status>Final</ns2:status>
					</ns2:tideCorrectors>
				</ns2:correctorFiles>
				<ns2:finalTides>
					<ns2:dateSubmitted>1904-01-01</ns2:dateSubmitted>
					<ns2:dateReceived>1904-01-01</ns2:dateReceived>
				</ns2:finalTides>
				<ns2:discussion>
</ns2:discussion>
				<ns2:comments/>
			</ns2:standard_or_ERZT>
			<ns2:VDATUM_or_constantSep used="false">
				<ns2:discussion xsi:nil="true"/>

				<ns2:comments/>
			</ns2:VDATUM_or_constantSep>
			<ns2:comments/>
		</ns1:verticalControl>
		<ns1:horizontalControl>
			<ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum>
			<ns2:projection>UTM Zone 14N</ns2:projection>
			<ns2:PPK xsi:nil="true" used="false"/>

			<ns2:PPP xsi:nil="true" used="false"/>

			<ns2:RTK xsi:nil="true" used="false"/>

			<ns2:DGPS used="true">
				<ns2:USCGStations>
					<ns2:name>Aransas Pass, 304kHz, ID: 816</ns2:name>
				</ns2:USCGStations>
				<ns2:discussion>DGPS correctors were monitored realtime during data collection for dropouts. No dropouts were witnessed during data collection. In addition to the realtime monitoring of DGPS corrections, position data were analyzed in the office during post-processing. The attitude editor within Caris HIPS and SIPS 9.0 was utilized to identify any position data that may be insufficient for final delivery. </ns2:discussion>
				<ns2:comments/>
			</ns2:DGPS>
			<ns2:comments/>
		</ns1:horizontalControl>
		<ns1:additionalIssues>
			<ns2:comments/>
		</ns1:additionalIssues>
	</ns1:verticalAndHorizontalControl>
	<ns1:resultsAndRecommendations>
		<ns1:chartComparison>
			<ns1:methods>
				<ns2:discussion>A chart comparison was conducted for H12761 using Caris HIPS and SIPS 9.0. Contours, as well as soundings, were compared against the largest scale RNC 11306 and ENC US5TX14M to accomplish the chart comparison. RNC 11306 and ENC US5TX14M do not cover the eastern region of H12761 and therefore RNC 11304 and ENC US4TX15M were included to complete the chart comparison. The methods and results of the comparison are detailed below. 

Contour Comparison Method:
Using the 2 meter CUBE weighted BASE surface, the 12 foot, 18 foot, 30 foot, and 60 foot contours were generated and displayed against the charted contours. Additionally, the 2 meter CUBE weighted BASE surface was viewed by a custom color band range based on the contour intervals (12ft, 18ft, 30ft, 60ft, 90ft, 120ft, 180ft). The results of the comparison are described below. 

Sounding Comparison Method:
Using the same 2 meter CUBE weighted BASE surface used for the contour comparison, spot soundings were generated in Caris HIPS and SIPS 9.0 for H12761. Soundings were displayed against the charted soundings and a visual comparison was made. The results are described below.

</ns2:discussion>
				<ns2:comments/>
			</ns1:methods>
			<ns1:charts>
				<ns2:rasterChart>
					<ns2:chart>
						<ns2:number>11306</ns2:number>
						<ns2:kapp>0</ns2:kapp>
						<ns2:scale>40000</ns2:scale>
						<ns2:edition>22</ns2:edition>
						<ns2:editionDate>2012-10</ns2:editionDate>
						<ns2:LNMDate>2015-09-01</ns2:LNMDate>
						<ns2:NMDate>2015-09-12</ns2:NMDate>
					</ns2:chart>
					<ns2:discussion>Contour Comparison Results:
The 12 foot contour has receeded shoreward, on average, approximately 20 meters from the charted contour.

The 18 foot contour has receeded shoreward, on average, approximately 100 meters from the charted contour. 

The 30 foot contour has receeded shoreward, on average, approximately 250 meters from the charted contour.

Sounding Comparison Results:
With exception to the differences identified through the contour comparison, in general, the soundings are in excellent agreement, with no major discrepancies. Soundings are generally within 1 foot (0.3m) of each other. Occasionally soundings differ by 2 to 3 feet, however generally depth differences appear to be minimal. Depth differences are not biased in any particular direction to support a systematic error. </ns2:discussion>
					<ns2:comments/>
				</ns2:rasterChart>
				<ns2:rasterChart>
					<ns2:chart>
						<ns2:number>11304</ns2:number>
						<ns2:kapp>0</ns2:kapp>
						<ns2:scale>80000</ns2:scale>
						<ns2:edition>14</ns2:edition>
						<ns2:editionDate>2012-04</ns2:editionDate>
						<ns2:LNMDate>2015-09-01</ns2:LNMDate>
						<ns2:NMDate>2015-09-12</ns2:NMDate>
					</ns2:chart>
					<ns2:discussion>Contour Comparison Results:
The results of the 12 foot, 18 foot, and 30 foot contour comparison with RNC 11304 match those of the RNC 11306 contour comparison.

The 60 foot contour has receeded shoreward, on average, approximately 650 meters from the charted contour.

Sounding Comparison Results:
Results of the sounding comparison with RNC 11304 match those of the RNC 11306 sounding comparison.</ns2:discussion>
					<ns2:images>
						<ns2:caption>H12761 Contour Comparison (Overview)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_CONTOURCOMPARISONOVERVIEW.JPG</ns2:link>
					</ns2:images>
					<ns2:images>
						<ns2:caption>H12761 Contour Comparison (12ft, 18ft, and 30ft Contour)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_CONTOURS_12_18_30.JPG</ns2:link>
					</ns2:images>
					<ns2:images>
						<ns2:caption>H12761 Contour Comparison (60ft Contour)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_CONTOUR_60.JPG</ns2:link>
					</ns2:images>
					<ns2:images>
						<ns2:caption>Sounding Comparison (RNC 11306)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_11306_SOUNDINGCOMPARISON.JPG</ns2:link>
					</ns2:images>
					<ns2:images>
						<ns2:caption>Sounding Comparison (RNC 11304)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_11304_SOUNDINGCOMPARISON.JPG</ns2:link>
					</ns2:images>
					<ns2:comments/>
				</ns2:rasterChart>
				<ns2:ENC>
					<ns2:chart>
						<ns2:name>US5TX14M</ns2:name>
						<ns2:scale>40000</ns2:scale>
						<ns2:edition>2</ns2:edition>
						<ns2:updateApplicationDate>2013-12-16</ns2:updateApplicationDate>
						<ns2:issueDate>2015-06-10</ns2:issueDate>
						<ns2:preliminary>false</ns2:preliminary>
					</ns2:chart>
					<ns2:discussion>The results of the chart comparison with ENC US5TX14M match those of the chart comparison with RNC 11306.</ns2:discussion>
					<ns2:comments/>
				</ns2:ENC>
				<ns2:ENC>
					<ns2:chart>
						<ns2:name>US4TX15M</ns2:name>
						<ns2:scale>80000</ns2:scale>
						<ns2:edition>10</ns2:edition>
						<ns2:updateApplicationDate>2014-02-07</ns2:updateApplicationDate>
						<ns2:issueDate>2015-06-10</ns2:issueDate>
						<ns2:preliminary>false</ns2:preliminary>
					</ns2:chart>
					<ns2:discussion>The results of the chart comparison with ENC US4TX15M match those of the chart comparison with RNC 11304. </ns2:discussion>
					<ns2:comments/>
				</ns2:ENC>
				<ns2:comments/>
			</ns1:charts>
			<ns1:AWOISItems>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No AWOIS Items were assigned for this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:AWOISItems>
			<ns1:maritimeBoundary>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:maritimeBoundary>
			<ns1:chartedFeatures>
				<ns2:results investigated="Investigated">
					<ns2:discussion>There were 5 charted features assigned to H12761. Each assigned feature is retained in the Final Feature File (FFF). Each feature in the FFF has been given a unique identifier in the "userid" field  of the .000 S-57 file (format H12761_XXX). Of the (5) assigned features the following determinations and recommendations were made:

DELETE: (4) assigned features were not found. A DELETE action is recommended. 

NOT ADDRESSED: (1) assigned feature was inshore of NALL. Not safe to address. 


</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:chartedFeatures>
			<ns1:unchartedFeatures>
				<ns2:results investigated="Investigated">
					<ns2:discussion>One new feature was found in H12761 and is included in the Final Feature File (FFF). The feature was given a unique identifier in the "userid" field of the .000 S-57 file (format H12761_XXX).  </ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:unchartedFeatures>
			<ns1:DTONS>
				<ns2:results reportSubmitted="false">
					<ns2:numberSubmitted xsi:nil="true"/>

					<ns2:discussion>There were no DTONs found in H12761. </ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:DTONS>
			<ns1:shoalAndHazardousFeatures>
				<ns2:results investigated="Investigated">
					<ns2:discussion>Bathymetric splits were acquired between set line spacing to adequately define shoals. Figure 17 displays a shoal where bathymetric splits were run. 

There are dynamic shoals around both the northern and southern jetty of the the Port Mansfield Channel. The shoal areas changed dramatically throughout the survey. Figure 18 and 19 detail the area of the dynamic shoal around the northen jetty . Figure 20 and 21 detail the area of the dynamic shoal around the southern jetty. Multiple depth changes are visible in the surface, however coverage in this area was deemed acceptable through correspondence with the Contracting Officer's Technical Representative (COTR). Reference Email Correspondence in Appendix II of this report. </ns2:discussion>
					<ns2:images>
						<ns2:caption>Bathymetric Splits Acquired to Define Shoal</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_BATHYMETRICSHOALSPLITS.PNG</ns2:link>
					</ns2:images>
					<ns2:images>
						<ns2:caption>Cross Section of Dynamic Shoal Area (Northern Jetty)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_NORTHERN_SHOAL_CROSSECTION.PNG</ns2:link>
					</ns2:images>
					<ns2:images>
						<ns2:caption>Plan View of Dynamic Shoal (Northern Jetty)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_NORTHERNDYNAMICSHOAL_OVERVIEW.PNG</ns2:link>
					</ns2:images>
					<ns2:images>
						<ns2:caption>Cross Section of Dynamic Shoal Area (Southern Jetty)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_SOUTHERN_SHOAL_CROSS_SECTION_CARIS.PNG</ns2:link>
					</ns2:images>
					<ns2:images>
						<ns2:caption>Plan View of Dynamic Shoal (Southern Jetty)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12761_SOUTHERNDYNAMICSHOAL_OVERVIEW.PNG</ns2:link>
					</ns2:images>
				</ns2:results>
				<ns2:comments/>
			</ns1:shoalAndHazardousFeatures>
			<ns1:channels>
				<ns2:results investigated="Investigated">
					<ns2:discussion>A safety fairway runs east-west through H12761. The surveyed depths within the safety fairway are in general agreement with the charted depths as detailed in the chart comparison section of this report. </ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:channels>
			<ns1:bottomSamples>
				<ns2:results investigated="Investigated">
					<ns2:discussion>5 bottom samples were obtained in accordance with sections 7.1 and 8.2 of the HSSD 2015 in areas designated by the feature object class springs (SPRING) in the Project Reference File (PRF). 
A brief description of the results is listed below.

H12761_A001: fine brown sand with soft grey mud
H12761_A002: fine brown sand with soft grey mud and broken shells
H12761_A003: fine brown sand with soft grey mud and broken shells
H12761_A004: fine brown sand with sticky grey mud and broken shells
H12761_A005: fine brown sand with sticky grey mud and broken shells

Detailed information and images of the bottom samples listed above are located in the Final Feature File (FFF). Each bottom sample has been given a unique identifier in the "userid" field of the .000 S-57 file (format H12761_AXXX). </ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:bottomSamples>
		</ns1:chartComparison>
		<ns1:additionalResults>
			<ns1:shoreline>
				<ns2:results investigated="Investigated">
					<ns2:discussion>A limited shoreline verification was preformed using the composite source file (CSF) provided with the project instructions. All assigned shoreline features were investigated except for 1 that was inshore of the NALL and unsafe to address. One new shoreline feature was found in H12761. All assigned and new shoreline features are encoded in the Final Feature File (FFF) and have been given a unique identifier in the "userid" field of the .000 S-57 file (format H12761_XXX).   </ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:shoreline>
			<ns1:priorSurveys>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No prior survey comparisons exist for this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:priorSurveys>
			<ns1:ATONS>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No Aids to navigation (ATONs) exist for this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:ATONS>
			<ns1:overheadFeatures>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No overhead features exist for this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:overheadFeatures>
			<ns1:submarineFeatures>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No submarine features exist for this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:submarineFeatures>
			<ns1:ferryRoutesAndTerminals>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:ferryRoutesAndTerminals>
			<ns1:platforms>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No platforms exist for this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:platforms>
			<ns1:significantFeatures>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No significant features exist for this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:significantFeatures>
			<ns1:constructionOrDredging>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:constructionOrDredging>
			<ns1:otherResults>
				<ns2:comments/>
			</ns1:otherResults>
			<ns1:newSurveyRecommendation>
				<ns2:results recommended="false">
					<ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:newSurveyRecommendation>
			<ns1:insetRecommendation>
				<ns2:results recommended="false">
					<ns2:discussion>No new insets are recommended for this area.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:insetRecommendation>
		</ns1:additionalResults>
	</ns1:resultsAndRecommendations>
	<ns1:approvalSheet>
		<ns1:statements>
			<ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision>
			<ns1:approval>All BASE surfaces, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval>
			<ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys and Specifications Deliverables Manual, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey>
			<ns1:additionalInfo xsi:nil="true"/>

		</ns1:statements>
		<ns1:signingPersonnel>
			<ns2:approverName>David R. Neff, C.H.</ns2:approverName>
			<ns2:approverTitle>VP of Survey, eTrac Inc.</ns2:approverTitle>
			<ns2:approvalDate>2015-11-30</ns2:approvalDate>
		</ns1:signingPersonnel>
	</ns1:approvalSheet>
</ns1:descriptiveReport>