File NHIR-2026-001 Prepared by Richard Fitts Distance 100 ft Method C-weighted (dBC)

Noise Harassment
Incident Log

Documented & electronically measured evidence · 3/30/2026 — 5/22/2026 · Source: White Sedan
CONFIDENTIAL EVIDENCE DO NOT REDISTRIBUTE
§01

Incident log

— of —

Morning Afternoon Evening Late/Early
#  Date  Time  Window  dBC  Source Notes Digestion
—
§02

Measurement methodology

All readings recorded at 100 feet from the road using a calibrated Raspberry Pi C-weighting measurement system. Sound intensity doubles every 10 dB — levels at the vehicle source are dramatically higher than recorded. OSHA mandates hearing protection above 85 dB; municipal ordinances typically cap property-line levels at 65–75 dB.

§03

Recording equipment & software

Microphone
Superlux TM58
  • High SPL handling · fast transient response
  • Maximum SPL rating: 155 dB
  • Peak reading in this log: 154.5 dBC — within rated range; no clipping occurred
  • Connected via USB audio interface to Raspberry Pi 4
Recording Platform
Raspberry Pi 4
  • 256 GB storage
  • Operating system: Raspberry Pi OS
  • Dedicated stationary placement · continuous monitoring
  • System clock maintained by Raspberry Pi OS
Calibration Reference Meter
DB-01 Professional Decibel Meter
  • A/C weighting switchable · Fast/Slow response modes
  • Measurement range: 30–130 dB
  • Used as reference standard to calibrate the Raspberry Pi / TM58 measurement system
  • Calibration offset in dbc_logger.py derived from side-by-side comparison with this meter
Software
dbc_logger.py
  • Custom Python application · Raspberry Pi OS
  • Digital C-weighting filter (IEC 61672-1) via SciPy
  • 48,000 Hz sample rate · 1-second measurement blocks
  • Logs both RMS dBC and peak dBC per event
  • Clipping detection on every block
  • Optional WAV clip capture at time of trigger
  • Configurable threshold, confirmation window, and cooldown
§04

Disclaimers & limitations

Purpose of record

These logs are being preserved for timing, recurrence, and relative event severity. The incident record documents a sustained pattern of bass-frequency harassment over an extended period, establishing frequency of occurrence, time-of-day distribution, and escalating or repeating intensity.

Measurement software

Recording software (dbc_logger.py) is currently being updated to apply a proper C-weighting filter per IEC 61672-1. All events logged at or above 93.0 dBC are captured and preserved in this record. The C-weighted dBC scale emphasizes low-frequency bass content and is the recognized standard for evaluating bass-frequency noise exposure.

Corroborating evidence

The logged events are further supported by physical damage, equipment disruption, resident signatures, and witness reports. The electronic incident log does not stand alone — it corroborates and timestamps a body of physical and testimonial evidence collected over the same period.

§05

Reference scale

Every recorded reading exceeds safe levels
150+ No safe exposure limit Extreme · painful
140 Fireworks · gunshots Hearing protection required
130 Jackhammers · ambulance sirens Dangerous under 30 seconds
120 Jet planes at takeoff Uncomfortable
110 Concerts · car horns Dangerous over 30 minutes
100 Snowmobiles · MP3 at full volume Very loud
90 Lawnmowers · power tools Permanent hearing loss over time
70 Traffic · vacuum cleaners Moderate
60 Normal conversation Soft

Where these readings land

Distribution of every logged incident, bucketed by 10 dB. Bars scale to the largest bucket in the current filter.

§06

Daily timeline

Each dot = 1 incident · color = severity · X axis = time of day
Date 00:00 06:00 12:00 18:00 24:00 Day total
< 100 dBC
100–119
120–139
140–149
150+
Empty rows = days with no logged incident in the current filter
§07

Adding new incidents

🔓 Unencrypted Loading…

Quick add — source auto-fills to White Sedan

Enter incidents one after another. The date stays sticky so you can log a whole day in a few keystrokes. Enter in the dBC field commits the row. Pending rows survive a page refresh. Save writes the encrypted log back to the OVH server.

Bulk paste or import a CSV file

Paste rows directly. Either form works:

2026-05-23,14:32,143.6
2026-05-23,18:11,148.2,White Sedan,northbound

CSV schema

Columns, in order:

id,date,time,dbc,source,notes
  • id auto-numbered if omitted
  • date = YYYY-MM-DD
  • time = HH:MM (24h)
  • dbc = decimal, e.g. 141.5
  • source defaults to White Sedan
  • Drag any CSV file onto the page to preview before saving.