<?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-K339-KR-16</ns2:number>
			<ns2:name>Offshore SW Pass</ns2:name>
			<ns2:generalLocality>Gulf of Mexico </ns2:generalLocality>
			<ns2:fieldUnit>eTrac Inc. </ns2:fieldUnit>
		</ns1:projectMetadata>
		<ns1:registryMetadata>
			<ns2:registryNumber>H12946</ns2:registryNumber>
			<ns2:sheetID>6</ns2:sheetID>
			<ns2:registryInstructions>Acquire assigned crossline lines and investigate assigned features.</ns2:registryInstructions>
			<ns2:sublocality>7 NM Southwest of Port Fourchon</ns2:sublocality>
			<ns2:stateOrTerritory>Louisiana </ns2:stateOrTerritory>
			<ns2:country>United States</ns2:country>
			<ns2:scale>20000</ns2:scale>
		</ns1:registryMetadata>
		<ns1:surveyMetadata>
			<ns2:year>2016</ns2:year>
			<ns2:chiefOfParty>David Neff, ACSM C.H. </ns2:chiefOfParty>
			<ns2:projectType>Basic Hydrographic Survey</ns2:projectType>
			<ns2:PIDate>2016-06-29</ns2:PIDate>
			<ns2:datesOfSurvey>
				<ns2:start>2016-09-10</ns2:start>
				<ns2:end>2016-09-11</ns2:end>
			</ns2:datesOfSurvey>
			<ns2:equipmentTypes>
				<ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment>
				<ns2:soundingEquipment></ns2:soundingEquipment>
				<ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment>
				<ns2:imageryEquipment></ns2:imageryEquipment>
			</ns2:equipmentTypes>
			<ns2:acquisition>
				<ns2:units>meters</ns2:units>
			</ns2:acquisition>
			<ns2:horizontalCoordinateSystem zone="15N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem>
			<ns2:timeZone>UTC</ns2:timeZone>
			<ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier>
			<ns2:titlesheetRemarks>
				<ns2:fieldRemarks>Registry Instructions: Acquire assigned crossline lines and investigate assigned features.  All times are UTC.  The extents of H12946 designate a newly proposed anchorage area about 7 nautical miles southwest of Port Fourchon.  The purpose of this resurvey is to detect any bathymetric or feature changes that may need to be addresses before the proposed anchorage area is approved and charted.  SUBCONSULTANT: Geodynamics LLC, 310A Greenfield Dr., Newport, NC 98570 SUBCONSULTANT: Theory Marine, 777 Viewcrest DR., Ventura, CA 93003 Projections: UTM 15N, WGS 84</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 Gulf of Mexico. H12946 covers approximately 7 square nautical miles of survey area. 43 lineal nautical miles were aquired during the survey. H12946 is irregular in geometry, and is approximately 2 nautical miles wide (E-W) by 5 nautical miles long (N-S) at its widest and longest lengths respectively.  

Survey was conducted within these limits on the assigned lines between September 10, 2016 (DN254) and Spetember 11, 2016 (DN255). </ns2:discussion>
			<ns2:limits>
				<ns2:northWest>
					<ns2:latitude hemisphere="N">29.032216</ns2:latitude>
					<ns2:longitude hemisphere="W">90.320920</ns2:longitude>
				</ns2:northWest>
				<ns2:southEast>
					<ns2:latitude hemisphere="N">28.950803</ns2:latitude>
					<ns2:longitude hemisphere="W">90.310747</ns2:longitude>
				</ns2:southEast>
			</ns2:limits>
			<ns2:images>
				<ns2:caption>Survey Limits (Black line) Assigned Lines (Blue)</ns2:caption>
				<ns2:link>SUPPORTFILES/H12946_SHEETLIMITS.JPG</ns2:link>
			</ns2:images>
			<ns2:comments>
				<ns2:fieldComment>
					<ns2:comment>Registry Instructions: Acuire assigned crosslines and investigate assigned features.  </ns2:comment>
					<ns2:initials></ns2:initials>
				</ns2:fieldComment>
			</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 2016 Edition (HSSD 2016). Survey was aquired along the assigned crossline and assigned features. </ns2:discussion>
			</ns2:results>
			<ns2:comments/>
		</ns1:surveyLimits>
		<ns1:surveyPurpose>
			<ns2:discussion>The extents of H12946 designate a newly proposed anchorage area, about 7 nautical miles southwest of Port Fourchon. This port services the majority of the Gulf of Mexico&apos;s deep water oil production and has a high concentration of vessel traffic. This area was last surved in 2006 and 2009 to object detection coverage stantards. The purpose of this resurvey is to detect any bathymetric or feature changes that may need to be addressed before the proposed anchorage area is approved and charted. Survey was acquired along the assigned crossline lines and assigned features. </ns2:discussion>
			<ns2:comments/>
		</ns1:surveyPurpose>
		<ns1:surveyQuality>
			<ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy>
			<ns2:discussion>Survey H12946 is accurate to IHO Order 1a as required per the HSSD 2016.</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 2016.  Depths in H12946 range from 9 to 18 meters. The assigned crosslines lines were acquired and the assigned features were investigated as stated in the Project Instructions. </ns2:discussion>
			</ns2:results>
			<ns2:comments/>
		</ns1:surveyCoverage>
		<ns1:coverageGraphic>
			<ns2:caption>Survey Coverage </ns2:caption>
			<ns2:link>SUPPORTFILES/H12946_SURVEY_COVERAGE.JPG</ns2:link>
		</ns1:coverageGraphic>
		<ns1:surveyStatistics>
			<ns2:LNM>
				<ns2:vesselLNM>
					<ns2:vessel>
						<ns2:hullID>Theory</ns2:hullID>
						<ns2:statistics>
							<ns2:MS_SBES>0</ns2:MS_SBES>
							<ns2:MS_MBES>46</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>5</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>46</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>5</ns2:XL_MBES_SBES>
					<ns2:XL_lidar>0</ns2:XL_lidar>
					<ns2:percentXLLNM>10.86</ns2:percentXLLNM>
				</ns2:totalLNM>
			</ns2:LNM>
			<ns2:totalSurveyStats>
				<ns2:bottomSamples>3</ns2:bottomSamples>
				<ns2:AWOIS>0</ns2:AWOIS>
				<ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints>
				<ns2:DP>0</ns2:DP>
				<ns2:diveOps>0</ns2:diveOps>
				<ns2:SNM>7</ns2:SNM>
			</ns2:totalSurveyStats>
			<ns2:surveyDates>2016-09-10</ns2:surveyDates>
			<ns2:surveyDates>2016-09-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 Theory</ns2:hullID>
					<ns2:LOA units="meters">11</ns2:LOA>
					<ns2:draft units="meters">0.75</ns2:draft>
				</ns1:vessel>
				<ns1:discussion>The M/V Theory  is a 11 meter aluminum catamaran equipped with an Universal Sonar Mount (USM) over-the-stern multibean mount, as well as an A-frame for SVP deployment.
</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.X2</ns2:model>
					<ns2:type>Sound Speed 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:discussion xsi:nil="true"/>

				<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 10.86%, 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.1. A 1 meter CUBE weighted BASE surface was created incorporating only the mainscheme and feature investigation lines, and excluded crosslines. 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. 
Note: This surface was created for QC only and is not submitted as a surface deliverable.

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 Order 1a compliance per beam. </ns2:discussion>
				<ns2:images>
					<ns2:caption>H12946 Crossline Comparison (1m)</ns2:caption>
					<ns2:link>SUPPORTFILES/H12946_CROSSLINE_COMPARISON.JPG</ns2:link>
				</ns2:images>
				<ns2:comments/>
			</ns1:crosslines>
			<ns1:uncertainty>
				<ns2:values>
					<ns2:soundSpeedUncertainty>
						<ns2:hullID>M/V Theory</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: The survey specific tide TPU values for measured and zoning tides are computed internally within TCARI. 

Standard deviation and uncertainty child layers of BASE surfaces were utilized during data processing to search for features, water column noise, and systematic errors. 

A custom child 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 child 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.1. The option &quot;Greater of the two&quot; 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. Each BASE surface&apos;s uncertainty QC report generated through the Caris QC Reporting tool is included in Separate II. 


The Total Propogated Uncertainty (TPU) was evaluated using the TPUTrac program in the AmiTrac program, developed in-house by eTrac Inc. The BASE surface&apos;s nodes were exported to an ASCII CSV file where the fields were (Easting, Northing, Depth, Uncertainty, Density) for each node. The CSV file was then loaded into the TPUTrac program and the TPU statistics were computed. A file was also created in this process to locate any points that exceed the allowable TPU, which was imported into Caris HIPS and SIPS 9.1 and any identified points from TPUTrac were analyzed and evaluated. 

For H12946 the following percentages represent the results of the TPU Testing:

Assigned Crossline Lines and Features MBES (Finalized 1m CUBE weighted BASE Surface) = 100% of nodes are within allowable TPU. 
</ns2:discussion>
				<ns2:images>
					<ns2:caption>H12946 Finalized 1m Assigned Crossline Lines and Features MBES TPU Statistics</ns2:caption>
					<ns2:link>SUPPORTFILES/H12946_TPUTRAC_1M_FINAL.JPG</ns2:link>
				</ns2:images>
				<ns2:comments/>
			</ns1:uncertainty>
			<ns1:junctions>
				<ns2:discussion>Depth differences between junctioning surveys were evaluated using the JunctionTrac program, developed in-house by eTrac Inc. For each junction, each BASE surface&apos;s nodes were exported to an ASCII CSV file where the fields were (Easting, Northing, Depth) for each node. A difference surface between the junctioning datasets was also created and exported to an ASCII CSV file where the fields were (Easting, Northing, Diff) for each node. The three ASCII CSV files were then loaded into the JunctionTrac program and junction statistics were computed. A file was also created in this process to locate any nodes from the difference surface that exceed the allowable TVU, which was imported into Caris HIPS and SIPS 9.1 and any identified points from JunctionTrac were analyzed. Note: the difference surfaces were created for comparison efforts only and are not submitted as a surface deliverable.</ns2:discussion>
				<ns2:junction>
					<ns2:survey>
						<ns2:registryNumber>H12049</ns2:registryNumber>
						<ns2:scale>10000</ns2:scale>
						<ns2:year>2009</ns2:year>
						<ns2:fieldUnit>C &amp; C Technologies, Inc.</ns2:fieldUnit>
						<ns2:relativeLocation>SW</ns2:relativeLocation>
					</ns2:survey>
					<ns2:discussion>H12946 junctions with H12049 to the Southwest. The junction comparison was performed using approximately 2,700m of overlapping data between H12946 and H12049. Depth differences were evaluated using the JunctionTrac program, developed in-house by eTrac Inc. 
Below is a histogram of junction comparison statistics showing the difference between the junctioning surfaces and allowable TVU.  99.9859% of nodes were within allowable TVU.  Survey H12946 and H12049 overlap a feature. The extreme outlier in the below graph is noted to be casued by this feature being represented slightly differently in the respective surfaces.  Junction comparison statistics are also included in Separate II.

</ns2:discussion>
					<ns2:images>
						<ns2:caption>H12946 - H12049 Junction Comparison</ns2:caption>
						<ns2:link>SUPPORTFILES/H12946_H12049_JUNCTION.JPG</ns2:link>
					</ns2:images>
					<ns2:comments/>
				</ns2:junction>
				<ns2:junction>
					<ns2:survey>
						<ns2:registryNumber>H11785</ns2:registryNumber>
						<ns2:scale>20000</ns2:scale>
						<ns2:year>2009</ns2:year>
						<ns2:fieldUnit>Leidos</ns2:fieldUnit>
						<ns2:relativeLocation>NW</ns2:relativeLocation>
					</ns2:survey>
					<ns2:discussion>H12946 junctions with H11785 to the North. The junction comparison was performed using approximately 2,700m of overlapping data between H12946 and H11785.Depth differences were evaluated using the JunctionTrac program, developed in-house by eTrac Inc. 
Below is a histogram of junction comparison statistics showing the difference between the junctioning surfaces and allowable TVU.  99.9967% of nodes were within allowable TVU.  Survey H12946 and H11785 overlap a feature that was not found in survey H12946. The extreme outlier in the below graph is noted to be casued by this feature only being represented in H11785.  Junction comparison statistics are also included in Separate II.</ns2:discussion>
					<ns2:images>
						<ns2:caption>H12946 - H11785 Junction Comparison</ns2:caption>
						<ns2:link>SUPPORTFILES/H12946_H11785_JUNCTION.JPG</ns2:link>
					</ns2:images>
					<ns2:comments/>
				</ns2:junction>
				<ns2:junction>
					<ns2:survey>
						<ns2:registryNumber>H11457</ns2:registryNumber>
						<ns2:scale>20000</ns2:scale>
						<ns2:year>2006</ns2:year>
						<ns2:fieldUnit>C &amp; C Technologies, Inc.</ns2:fieldUnit>
						<ns2:relativeLocation>SE</ns2:relativeLocation>
					</ns2:survey>
					<ns2:discussion>H12946 junctions with H11457 to the East. The junction comparison was performed using approximately 1,300m of overlapping data between H12946 and H11457. Depth differences were evaluated using the JunctionTrac program, developed in-house by eTrac Inc. 
Below is a histogram of junction comparison statistics showing the difference between the junctioning surfaces and allowable TVU.  90.3640% of nodes were within allowable TVU.  Survey H12946 and H11457 overlap a feature that was not found in survey H12946. The extreme outlier in the below graph is noted to be casued by this feature only being represented in H11457.  Survey H11475 was aquired in 2006. The lower percentage is likely caused by the time period between the two surveys. Junction comparison statistics are also included in Separate II.</ns2:discussion>
					<ns2:images>
						<ns2:caption>H12946 - H11457 Junction Comparison </ns2:caption>
						<ns2:link>SUPPORTFILES/H12946_H11457_JUNCTION.JPG</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 Day to Day SVP Comparison (DN254)</ns2:caption>
					<ns2:link>SUPPORTFILES/H12946_SVP_TH_DN254.JPG</ns2:link>
				</ns1:images>
				<ns1:images>
					<ns2:caption>Example of Day to Day SVP Comparison (DN254 &amp; DN255)</ns2:caption>
					<ns2:link>SUPPORTFILES/H12946_SVP_TH_DN254_DN255.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 in the AmiTrac program, developed in-house by eTrac Inc. Each finalized BASE surface&apos;s nodes were exported to an ASCII CSV file where the fields were (Easting, Northing, Depth, Uncertainty, Density) for each node. The CSV file was then loaded into the DensityTrac program and density statistics were computed. 

For H12946 the following percentages represent the results of the density testing:

Assigned Crossline Lines and Features MBES (Finalized 1m CUBE weighted BASE Surface) = 99.1234% of nodes are composed from at least 5 soundings. 

 </ns2:discussion>
					<ns2:images>
						<ns2:caption>H12946 Finalized 1m Assigned Crossline Lines and Features MBES Density Distribution Statistics</ns2:caption>
						<ns2:link>SUPPORTFILES/H12946_DENSITYHISTOGRAM_1M_FINAL.JPG</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.1 to ensure collection criteria had been met. Shown below is an example of the unprocessed backscatter mosaic from H12946 DN255.</ns2:discussion>
				<ns2:images>
					<ns2:caption>Raw Backscatter From M/V Theory (DN255)</ns2:caption>
					<ns2:link>SUPPORTFILES/H12946_BACKSCATTER_TH_DN255.JPG</ns2:link>
				</ns2:images>
			</ns2:results>
			<ns2:comments/>
		</ns1:backscatter>
		<ns1:dataProcessing>
			<ns1:softwareUpdates>
				<ns1:featureObjectCatalog>NOAA Profile V_5_4</ns1:featureObjectCatalog>
				<ns1:discussion xsi:nil="true"/>

				<ns1:comments/>
			</ns1:softwareUpdates>
			<ns1:surfaces>
				<ns1:surface>
					<ns2:surfaceName>H12946_MB_1m_MLLW_Final</ns2:surfaceName>
					<ns2:surfaceType>BAG</ns2:surfaceType>
					<ns2:resolution units="meters">1</ns2:resolution>
					<ns2:depthRange>
						<ns2:min units="meters">9.14</ns2:min>
						<ns2:max units="meters">17.33</ns2:max>
					</ns2:depthRange>
					<ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter>
					<ns2:purpose>Complete MBES</ns2:purpose>
				</ns1:surface>
				<ns1:surface>
					<ns2:surfaceName>H12946_MB_1m_MLLW</ns2:surfaceName>
					<ns2:surfaceType>BAG</ns2:surfaceType>
					<ns2:resolution units="meters">1</ns2:resolution>
					<ns2:depthRange>
						<ns2:min units="meters">10.21</ns2:min>
						<ns2:max units="meters">17.33</ns2:max>
					</ns2:depthRange>
					<ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter>
					<ns2:purpose>Complete MBES</ns2:purpose>
				</ns1:surface>
				<ns1:discussion>In areas shoaler than 20 meters, a 1m surface is provided meeting specifications set forth in the Project Instructions. The 1m surface covers the entire survery area of H12946 as all soundings within the survey limits are shoaler than 20 meters. 

A parent surface of the 1m surface is provided. The 1m parent surface covers the entire survey area of H12946. </ns1:discussion>
				<ns1:images>
					<ns2:caption>H12946 Delivered BASE Surface Coverage Graphic </ns2:caption>
					<ns2:link>SUPPORTFILES/H12946_SURFACES_COVERAGE.JPG</ns2:link>
				</ns1:images>
				<ns1:comments/>
			</ns1:surfaces>
			<ns1:additionalDataProcessing>
				<ns2:comments/>
			</ns1:additionalDataProcessing>
		</ns1:dataProcessing>
	</ns1:dataAcquisitionAndProcessing>
	<ns1:verticalAndHorizontalControl>
		<ns1:discussion/>
		<ns1:verticalControl>
			<ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum>
			<ns2:standard_or_ERZT used="true">
				<ns2:methodsUsed>TCARI</ns2:methodsUsed>
				<ns2:tideStations/>
				<ns2:correctorFiles>
					<ns2:waterLevels>
						<ns2:fileName>8760922.tid</ns2:fileName>
						<ns2:status>Final Approved</ns2:status>
					</ns2:waterLevels>
					<ns2:waterLevels>
						<ns2:fileName>8761724.tid</ns2:fileName>
						<ns2:status>Final Approved</ns2:status>
					</ns2:waterLevels>
					<ns2:waterLevels>
						<ns2:fileName>8762075.tid</ns2:fileName>
						<ns2:status>Final Approved</ns2:status>
					</ns2:waterLevels>
					<ns2:tideCorrectors>
						<ns2:fileName>K339KR2016Final.tc</ns2:fileName>
						<ns2:status>Final</ns2:status>
					</ns2:tideCorrectors>
				</ns2:correctorFiles>
				<ns2:finalTides>
					<ns2:dateSubmitted>2016-09-20</ns2:dateSubmitted>
					<ns2:dateReceived>2016-10-25</ns2:dateReceived>
				</ns2:finalTides>
				<ns2:discussion>In order to reference soundings to MLLW, the Tidal Constituent And Residual Interpolator (TCARI) method was applied to the HDCS data via the TCARI program. TCARI compiled information from SW Pass, LA (8760922), Grand Isle, LA (8761724), and Port Fourchon, LA (8762075). 

Note: Any vertical control method deviations from the Project Instructions are addressed in the DAPR.</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>World Geodetic System of 1984 (WGS84)</ns2:horizontalDatum>
			<ns2:projection>UTM Zone 15N</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>English Turn, 293kHz, ID: 814</ns2:name>
				</ns2:USCGStations>
				<ns2:discussion>During main acquisition M/V Theory received GNSS satellite corrections over the POS MV G2 carrier signal from the Marinestar Global Correction System maintained by Fugro. The Marinestar system is a global realtime GNSS broadcast system that delivers corrections from an array of base stations around the world via geo-stationary satellites. Corrections were monitored realtime during data acquisition to ensure no dropouts occurred and the POSMV maintained differential accuracies throughout the survey. No dropouts were witnessed during data collection. Position data were analyzed in the office during post-processing. The attitude editor within Caris HIPS and SIPS 9.1 was utilized to identify any position data that may be insufficient for final delivery.

DGPS stations were only to be used as a backup horizontal correction source. G2 Marinestar correctors were used as the primary correction source. DGPS was never utilized, as G2 corrections were available throughout all survey operations</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 H12946 using Caris HIPS and SIPS 9.1. Soundings were compared against the largest scale RNC 11346 and ENC US5LA26M to accomplish the chart comparison.  RNC 11346 and ENC US5LA26M  do not cover the western half of H12946, and therefore RNC 11357 and ENC US4LA29M were included to complete the chart comparison. The methods and results of the comparison are detailed below. The methods and results of the comparison are detailed below. 

Contour Comparison Method:
No contours are present in RNC 11346 and ENC US5LA26M or RNC 11346 and ENC US5LA26M, within the survey limits of H12946, therefore no contour comparisons were conducted.

Sounding Comparison Method:
Using the 1 meter CUBE weighted BASE surface, spot soundings were generated in Caris HIPS and SIPS 9.1 for H12946. 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>11346</ns2:number>
						<ns2:kapp>0</ns2:kapp>
						<ns2:scale>40000</ns2:scale>
						<ns2:edition>5</ns2:edition>
						<ns2:editionDate>2014-03</ns2:editionDate>
						<ns2:LNMDate>2016-05-18</ns2:LNMDate>
						<ns2:NMDate>2016-05-22</ns2:NMDate>
					</ns2:chart>
					<ns2:discussion>Sounding Comparison Results:
In general, the soundings are in excellent agreement, with no major discrepencies. Soundings are generally within 1 foot of each other. Occasionally soundings differ by 2 to 3 feet, however depth differences generally 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>11357</ns2:number>
						<ns2:kapp>0</ns2:kapp>
						<ns2:scale>80000</ns2:scale>
						<ns2:edition>43</ns2:edition>
						<ns2:editionDate>2014-05</ns2:editionDate>
						<ns2:LNMDate>2016-06-07</ns2:LNMDate>
						<ns2:NMDate>2016-06-18</ns2:NMDate>
					</ns2:chart>
					<ns2:discussion>Sounding Comparison Results:
In general, the soundings are in excellent agreement, with no major discrepencies. Soundings are generally within 1 foot of each other. Occasionally soundings differ by 2 to 3 feet, however depth differences generally appear to be minimal. Depth differences are not biased in any particular direction to support a systematic error. </ns2:discussion>
					<ns2:images>
						<ns2:caption>Sounding Comparison (RNC 11346) </ns2:caption>
						<ns2:link>SUPPORTFILES/H12946_RNC11346_SOUNDINGCOMPARISON.JPG</ns2:link>
					</ns2:images>
					<ns2:images>
						<ns2:caption>Sounding Comparison (RNC 11357)</ns2:caption>
						<ns2:link>SUPPORTFILES/H12946_RNC11357_SOUNDINGCOMPARISON.JPG</ns2:link>
					</ns2:images>
					<ns2:comments/>
				</ns2:rasterChart>
				<ns2:ENC>
					<ns2:chart>
						<ns2:name>US5LA26M</ns2:name>
						<ns2:scale>40000</ns2:scale>
						<ns2:edition>24</ns2:edition>
						<ns2:updateApplicationDate>2014-07-15</ns2:updateApplicationDate>
						<ns2:issueDate>2016-04-26</ns2:issueDate>
						<ns2:preliminary>false</ns2:preliminary>
					</ns2:chart>
					<ns2:discussion>The results of the chart comparison with ENC US5LA26M match those of the chart comparison with RNC 11346. </ns2:discussion>
					<ns2:comments/>
				</ns2:ENC>
				<ns2:ENC>
					<ns2:chart>
						<ns2:name>US4LA29M</ns2:name>
						<ns2:scale>80000</ns2:scale>
						<ns2:edition>19</ns2:edition>
						<ns2:updateApplicationDate>2014-11-26</ns2:updateApplicationDate>
						<ns2:issueDate>2016-04-25</ns2:issueDate>
						<ns2:preliminary>false</ns2:preliminary>
					</ns2:chart>
					<ns2:discussion>The results of the chart comparison with ENC US5LA29M match those of the chart comparison with RNC 11357. </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 3 charted features assigned to H12946. Each assigned feature is retained in the Final Feature File (FFF). Each feature in the FFF has been given a unique identifier in the &quot;userid&quot; field  of the .000 S-57 file (format H12946_XXX). Refer to the FFF for determinations and recommendations of each feature.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:chartedFeatures>
			<ns1:unchartedFeatures>
				<ns2:results investigated="Investigated">
					<ns2:discussion>There was 1 new feature found in H12946 and added to the Final Feature File (FFF). Each feature in the FFF has been given a unique identifier in the &quot;userid&quot; field of the .000 S-57 file (format H12946_XXX). Refer to the FFF for determinations and recommendations of each feature.

There were 2 uncharted features assigned to H12946. Each assigned feature is retained in the FFF. Each feature in the FFF has been given a unique identifier in the &quot;userid&quot; field of the .000 S-57 file (format H12946_XXX). Refer to the FFF for determinations and recommendations of each feature.
Note: Both assigned, uncharted features are listed as BSEE Wellheads. </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 this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:DTONS>
			<ns1:shoalAndHazardousFeatures>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No shoals or potentially hazardous features exist for this survey.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:shoalAndHazardousFeatures>
			<ns1:channels>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No channels exist for this survey. There are no designated anchorages, precautionary areas, safety fairways, traffic separation schemes, pilot boarding areas, or channels and range lines within the survey limits.</ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:channels>
			<ns1:bottomSamples>
				<ns2:results investigated="Investigated">
					<ns2:discussion>3 bottom samples were obtained in accordance with sections 7.2 and 7.2.2 of the HSSD 2016 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.

H12946_F001: soft, grey, clay
H12946_F002: soft, grey, mud with soft, grey, clay
H12946_F003: soft, grey, clay

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 &quot;userid&quot; field of the .000 S-57 file (format H12946_FXXX). </ns2:discussion>
				</ns2:results>
				<ns2:comments/>
			</ns1:bottomSamples>
		</ns1:chartComparison>
		<ns1:additionalResults>
			<ns1:shoreline>
				<ns2:results investigated="None Exist">
					<ns2:discussion>No shoreline exists for this survey.</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>2016-12-05</ns2:approvalDate>
		</ns1:signingPersonnel>
	</ns1:approvalSheet>
</ns1:descriptiveReport>