22.01.2015 Views

(IVAR) - Final Report - Strategic Environmental Research and ...

(IVAR) - Final Report - Strategic Environmental Research and ...

(IVAR) - Final Report - Strategic Environmental Research and ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ecord the time, Track ID, <strong>and</strong> other parameters on their field data sheet. Otherwise, the RFC<br />

was recorded as a non-confirmation.<br />

Another procedural change made during the fall 2008 studies was to the have the visual<br />

observers return to the same VT sites for each session during a study. This was done in<br />

expectation that it would eliminate one variable – familiarity with the environment at the site,<br />

especially the location of the radar beam above the site – from the challenging task of visually<br />

confirming birds tracked by the radar.<br />

At least one member from each team participated in a post-processing meeting immediately after<br />

the field sessions. At these meetings the teams compared the information on their respective<br />

field data forms for consistency. It was critical that RFCs were recorded consistently <strong>and</strong><br />

accurately by all the teams. The RFC Number was the key to linking the VT’s visual<br />

observation of a target on the wing with the RT’s observations of the track for that target on the<br />

radar display. The unique Track ID of a target called in an RFC was also recorded on the RT<br />

data forms. It provided the link between the RT <strong>and</strong> VT observations of the targets <strong>and</strong> the data<br />

recorded in the digital plots <strong>and</strong> tracks files generated by the DRP.<br />

During these post-processing sessions the field data sheets were sometimes updated (<strong>and</strong> soannotated)<br />

to reflect results of RFCs other than “Y” for Confirmed or “No” for Not Confirmed.<br />

The other outcomes of an RFC included: “A” – the RFC was Aborted before a team had time to<br />

confirm the target; “H” – the team to which the RFC was directed did not Hear the broadcast,<br />

usually because of noise from passing aircraft; “O” – for Other events that interfered with the<br />

completion of the RFC (e.g., the DRP was accidentally unplugged after an RFC was broadcast).<br />

Only RFCs recorded as “Y” or “N” were used in the computation of the Success Criterion for<br />

visual confirmations.<br />

The field data were subjected to extensive quality control procedures during <strong>and</strong> after they were<br />

transcribed from the hardcopy field forms into a relational database. The field observations were<br />

also checked against two types of radar data: The digital picture that was captured when each<br />

RFC was broadcast, <strong>and</strong> by replaying the plots <strong>and</strong> tracks data for that time period to ensure the<br />

radar <strong>and</strong> visual observations were consistent.<br />

Results<br />

Table 6-2 summarizes the results of the <strong>IVAR</strong> visual confirmation studies. Fifty 2-hour sessions<br />

were conducted at a total of 34 separate visual observation sites located at the four geographic<br />

study locations. Visual observers confirmed targets over horizontal distances that ranged from 0<br />

to >5100 meters (0-17,000 feet; see also 6.1.1.5) <strong>and</strong> through 360° of azimuth (see also 6.2.1.2).<br />

The visual observers identified the 1531 confirmed targets as belonging to 65 separate taxa, with<br />

the most frequently observed taxa being gulls (Subfamily Larinae), Turkey Vultures, <strong>and</strong><br />

Double-crested Cormorants. Approximately half (841) of the targets were single birds; the<br />

remainder (702) were flocks of two or more birds. Of the 1531 total confirmation tracks, 132<br />

were confirmed by two or more Visual Teams.<br />

68

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!