Match the Sturgis Airport and Aircraft in an Injury-Record Inquiry

Confirm the Kentucky airport before matching a name

Retain the airport name, state and identifier shown in the material connected with the event. The Kentucky Transportation Cabinet directory lists Sturgis Municipal Airport with TWT as its identifier. That is a useful local name check, not evidence that an individual used the airport. Compare it with an actual itinerary, message or other document rather than treating a town-name search as confirmation. Keep a departure point, planned destination and physical injury scene separately identified. If an event happened elsewhere on a trip associated with Sturgis, preserve that location instead of moving the scene to the airport to match a search result.

Describe the activity and precise part of the site

Write what the person was doing immediately before the event, using their account and any original image already available. Distinguish approaching an aircraft, boarding, being on a flight, handling items and walking in a ground area. Identify an entrance, vehicle, aircraft position or other supported feature without guessing a restricted-area name. A booking describes a planned journey; it does not prove that boarding or departure occurred. An airport directory also cannot identify the organization controlling a particular activity. Mark the limits of a witness's view and keep a later explanation distinguishable from what that witness actually observed.

Preserve the aircraft reference and the organization names separately

If an existing photograph or document shows an aircraft registration, retain the whole source and note any unclear character. Keep the aircraft make or model exactly as supported rather than identifying it from a remembered color scheme. Record the business or person named on a booking, receipt or communication under the role that document states. An aircraft identifier, a booking provider and the organization described as an operator are different references to confirm. Do not enter a restricted area or approach an aircraft to fill a documentation gap. A supported identifier is useful even when another part of the account remains uncertain.

Use the published NTSB search fields for their stated purpose

NTSB's Aviation Investigation Search page identifies a database covering civil aviation accidents and selected incidents and provides separate fields for city, state, aircraft registration, airport name and airport code. Prepare the facts you can support before using those filters. Do not choose a result merely because its narrative mentions Sturgis, and do not infer that every injury connected with an airport will have an NTSB entry. This research read the public instructions without running an individual event query. A missing result would need its search scope considered; it would not by itself establish that no injury or response occurred.

Keep event dates and publication dates distinguishable

The search page also separates event-date fields from publication-date and report-status fields. Preserve the date and status printed on any actual report you receive, together with its case reference. A later publication should not silently become the date of the event. Likewise, an amended document needs to remain distinguishable from the version previously saved. If a result concerns a similar aircraft or nearby location on another date, keep it outside the event chronology until the relationship is confirmed. A precise match should rest on several supported identifiers rather than a single familiar word in a narrative.

Read an investigation document within its actual scope

NTSB's process page distinguishes gathering facts, analysis and acceptance of a final report. That framework explains why document status and purpose matter when organizing a file. Retain a factual account, a later analysis and the agency's final report under their own titles if those materials actually exist for the event. Do not turn one excerpt into your own technical conclusion about equipment, weather or a person's actions. The agency's CAROL link redirected to a page with no readable content in this research, so its current interactive workflow and any individual docket were not tested.

Build an index around the confirmed event and unresolved matches

Place the supported airport, aircraft reference, activity, event date and original communications at the front of the file. Add a report only with its issuing organization, identifier and status. Keep care findings attributed to the actual provider and distinguish an agency record from a private business or employment document. State which match or requested item remains unresolved. AskLegalMatters offers information and lead connections without affiliation with the airport, KYTC or NTSB. An appropriate professional can assess technical, medical and legal questions; identifying an aviation entry does not determine fault, clinical cause or an injury outcome.

Official sources and verification notes

Related local and state guidance

Existing city injury guides · Kentucky state resources · More dedicated locality articles