JOE BRIGHAM INC
Also recorded as: JBI HELICOPTER SERVICES, JOE BRIGHAM INC, Joe Brigham Inc.
Accident & enforcement record
Events that happened, regardless of the operator's own reporting. Each links to its public source.
NTSB accidents & incidents
Operated by Joe Brigham Inc. (per NTSB report)
Not yet finalized — may be revised.The pilot’s loss of control during the initial climb in dark night conditions due to spatial disorientation, which resulted in a steep banking descent into trees and terrain. Contributing to the accident was the pilot’s lack of recent night flight experience, improper cockpit lighting settings, and his failure to use the helicopter’s stability augmentation system before and during the unusual attitude.
Operated by JOE BRIGHAM INC (per NTSB report)
The pilot's failure to center the sling load prior to commencing forward flight. Also causal, was the pilot's improper decision to attempt a takeoff with a quartering tailwind, which resulted in an engine compressor stall.
Operated by JOE BRIGHAM INC. (per NTSB report)
The pilot's failure to maintain control of the helicopter during an aerial application maneuver. This put the helicopter in a low slow down wind, high power demand turn, where it encountered a loss of tail rotor effectiveness, and the subsequent collision with the marsh.
FAA enforcement actions
No FAA enforcement actions linked to this operator.
Maintenance disclosure history
Service Difficulty Reports are self-reported maintenance findings. The NUMBER of reports is not a measure of reliability — diligent operators file more, not fewer. These are shown for transparency, not as a negative signal. To verify a report, search its control number at the FAA SDRS site.
Reports span 2011–2025. Most-reported systems: Main rotor (62) — 1; Tail rotor drive (65) — 1; Engine (72) — 1. Most-common natures of condition, as filed: OTHER — 2; OVER TEMP; WARNING INDICATION — 1.
3 reports on file.
Part: DRIVE SHAFT — CRACKED (TAIL ROTOR) · airframe 9,024 hrs · 8,537 cycles
DURING 12 MONTH INSPECTION FOUND CRACKS RADIATING FROM WHERE THE RIVETS ARE INSTALLED ON EITHER END ON ONE OF THE SEGMENTED RIVETED DRIVE SHAFT ASSEMBLY. THIS WAS DETECTED WITH A 10X MAGNIFYING GLASS. THE OTHER SEGMENTED SHAFTS CHECKED OUT OK. PART WITH REPLACED WITH A NEW ONE AND THE OTHER RED TAGGED
Part: COMBUSTION CASE — CRACKED (ENGINE) · airframe 14,278 hrs · 11,173 cycles
NOTED A HIGH TOT INDICATION ON APPROACH TO LAND AT HOME STATION. VISUALLY INSPECTED AND FOUND CRACK IN OUTER COMBUSTION CASE ASSEMBLY.
Part: BLADE — CRACKED (MAIN ROTOR)
A CRACK WAS FOUND ON 1 OF THE MAIN ROTOR BLADES L/E ABRASION STRIP DURING A ROUTINE 30 DAY/50 HR INSP. CRACK IS 65MM IN LENGTH AND LOCATED 6` 4" FROM BLADE ROOT, TOP SECTION OF L/E. REMOVED BLADE FOR REPAIR BY MFG CERTIFIED BLADE REPAIR SHOP. `
Linked aircraft
| N-number | Make / model | Year | Status | Link basis |
|---|---|---|---|---|
| N2611 | BELL HELICOPTER TEXTRON 206L-1 | 1980 | Valid Registration | Operator named in NTSB report |
| N407JB | BELL 407 | 1998 | Valid Registration | Matched by certificate designator |
| N444JB | BELL OH-58A | 1971 | Valid Registration | Operator named in NTSB report |
| N445JB | — | — | Matched by certificate designator | |
| N64JB | BELL 206B | 1978 | Valid Registration | Matched by certificate designator |
| N800JB | BELL 206B | 1979 | Valid Registration | Matched by certificate designator |
| N801JB | BELL 206B | 1979 | Valid Registration | Matched by certificate designator |
| N802JR | — | — | Matched by certificate designator | |
| N803JB | BELL 206B | 1991 | Valid Registration | Matched by certificate designator |
| N868JB | BELL 206B | 2000 | Valid Registration | Matched by certificate designator |
Aircraft with earlier records under this certificate
Maintenance and accident records on this page also cover aircraft that are not in this operator's current FAA fleet list. Charter and management fleets change — owners switch management companies, sell, or export aircraft. Where the registry shows what became of a tail, it is noted below.
1 aircraft filed records under this certificate within the last two years but are not in the fleet list we hold — fleet lists can lag actual operations.