{
  "id": "1999-januaryfebruary-colliding-databases-816",
  "slug": "1999-januaryfebruary-colliding-databases-816",
  "url": "https://dwillis.github.io/uplink/article/1999-januaryfebruary-colliding-databases-816.html",
  "year": 1999,
  "month": "January/February",
  "monthNum": 1,
  "headline": "Colliding databases (#816)",
  "kicker": "",
  "author_name": "Elizabeth Marchak",
  "author_title": "",
  "affiliation": "The Plain Dealer",
  "summary": "Aviation reporting requires meticulous research, developing reliable sources, understanding FAA and NTSB databases, and filing FOIA requests to uncover safety issues and regulatory violations. Journalists must verify data thoroughly, avoid deadline mistakes, and build credibility with the aviation community.",
  "keywords": [
    "aviation",
    "reporting",
    "databases"
  ],
  "topics": [
    "Investigative Methods",
    "Public Safety",
    "Data & Databases"
  ],
  "technologies": [],
  "full_text": "Colliding databases (#816)\nBy Elizabeth Marchak\nThe Plain Dealer\n\nAviation reporting is complicated and time-consuming. The computer makes it even more so. A few notes of caution: Don't wait until deadline. Learn what offices the FAA, the NTSB and the IG have in your area. If they hang up, don't give up. The aviation community has a low opinion of reporters. You have to convince them you are serious.\n\nDevelop sources you never quote. People you can double-check your findings with are more valuable than anybody who can give you a pithy quote on deadline. Secret sources are your reality check.\n\nHave a plane crash plan in place in your newsroom. Know how your community plans to respond. Develop contacts at the NTSB, which investigates plane crashes (not the FAA). Learn the schedule for the release of reports and opening of dockets.\n\nKnow how to search for accidents and incident data. Know how to search for a whole fleet using the four-digit OP code, or operator code. (Computer data for one plane is rarely sufficient and is unfair to the operator.) Know ATA or airplane system codes. Know how to search for N-numbers and serial numbers. (A tail number or an N-number may change, but a serial number shouldn't.) And learn the lingo, but keep it out of your stories. Learn to put repairs and problems in context. A rash of reports of lavatory and exit lights problems are far less serious than air returns for lack of radar. Remember, it's what isn't reported that is often the real problem. Don't use data on deadline you never seen before. There's a really good reason Web pages have disclaimers about completeness they really don't have everything. Many news organizations have ignored these warnings and shoved data into the paper or on the air, making huge mistakes, missing important angles or ruining their credibility with potential sources in the process.\n\nFile FOIAs on every single aviation entity in your area. This is the best way to find out who has been inspected and when, who has been \"violated\" (FAA slang for who has been investigated for violating regulations), and what action the FAA took. File for every single significant event, too. There are FOIA officers out there who love a well-written request on something nobody else is paying attention to, so let er rip.\n\nElizabeth Marchak can be reached by e-mail at marchak@digex.com",
  "provenance": {
    "extracted_by": "anthropic/claude-sonnet-4-6",
    "extracted_at": "2026-07-05",
    "verified": true
  },
  "similar": [
    {
      "slug": "1996-december-you-get-what-you-pay-for",
      "score": 0.335
    },
    {
      "slug": "2002-february-data-2",
      "score": 0.299
    },
    {
      "slug": "2002-february-data",
      "score": 0.288
    },
    {
      "slug": "2000-march-nicar-databases-as-of-feb-1-2000-2",
      "score": 0.251
    },
    {
      "slug": "2002-february-tipsheets-2",
      "score": 0.239
    }
  ],
  "html_url": "https://dwillis.github.io/uplink/article/1999-januaryfebruary-colliding-databases-816.html",
  "json_url": "https://dwillis.github.io/uplink/article/1999-januaryfebruary-colliding-databases-816.json"
}