Woodfibre LNG open houses · November and December 2026 · 4:30–7:30 p.m. Pacific
The application now gives flare geometry. Will you confirm that it matches the installed equipment and publish the governing tip design, capacity, gas composition and exit conditions, together with the accepted Flaring Management Report and its engineering attachments?
Records to ask for · Current installed-design drawings, source table, report revision, acceptance correspondence and any written exemptions.
The application models up to 38 days of commissioning flaring. Over how many calendar months could that happen? How many hours of flaring and what volume of gas do you expect in each stage, including if startup has to be repeated?
Records to ask for · Current commissioning schedule, hourly or finer release profiles, total event volumes, uncertainty ranges and comparable-project operating evidence.
How do the proposed continuous HP/LP source rates fit the phrase “no routine flaring”? Which enforceable document defines the term here, and how are pilots, purge gas, passing valves, compressor seals and loading counted?
Records to ask for · Applicable permit clauses, definitions, approved operating measures and reporting categories.
The notice lists process upset and restart events of up to 24 hours and venting after a thermal oxidizer trip of up to 48 hours. How often do you expect each event? What happens if power is lost or the equipment takes longer to restart?
Records to ask for · Scenario register, shutdown logic, backup-power and recycle capability, event release timelines, safeguards and current vendor guarantees.
The notice reports fine particles and total volatile organic compounds (VOCs). How much soot and benzene do you expect during a flare? During unburned venting, how much benzene and hydrogen sulphide could reach each community? Which pollutants have ambient objectives, permit limits or reporting requirements?
Records to ask for · Current source inventory in g/s and event mass, species breakdown, fuel sulfur, particle-size/soot information, combustion performance and a pollutant-by-pollutant authorization table.
What ground-level concentrations did your model predict for Britannia Beach, the estuary and each Squamish neighbourhood? Can you share the results by location and averaging period, with the wind direction, inversion conditions and background pollution for the highest values?
Records to ask for · Community coordinates, peak concentrations by pollutant and averaging period, a map of modelled locations, and the weather and background data for peak hours.
Will you show total concentrations from Woodfibre, the FortisBC compressor station, vessels and other relevant local sources, with existing air pollution included? Which overlapping startup, upset and shipping cases were assessed, and why?
Records to ask for · Cumulative source inventory, shipping/loading schedules, background-selection method, concurrent-event cases and separate permit identifiers.
What continuous monitors will operate in town and along the transport corridor before, during and after startup? Who owns and quality-checks the data, how soon will it be public, and will an independent party have access to the raw records?
Records to ask for · Monitoring plan, station and inlet locations/heights, pollutants and detection limits, uptime targets, calibration, data ownership, public feed and permanent archive.
Who checks an exceedance, who receives it and how quickly? What triggers investigation, operating changes and public advice? Will original readings, corrected data, permit contraventions and corrective actions remain publicly accessible?
Records to ask for · Pollutant-specific thresholds and averaging periods, reporting deadlines, responsible agencies, public communication procedure and corrective-action record.
Will you publish the accepted Flaring Notification Plan and show exactly how residents receive planned-event notices, unexpected-event updates and any health advice? Who is responsible, including outside business hours?
Records to ask for · Accepted notification plan, delivery channels, contact responsibilities, language/access provisions, update triggers and a sample public event report.