WELL · 42-005-30383 · DISTRICT 6

Flournoy Ruby #1

Plugged

Angelina County · Manning (Bossier Sand) field  · Vertical

Flournoy Ruby #1 (API 42-005-30383) is a plugged well in Angelina County, plugged November 18, 2024, last operated by Bbx Operating L.L.C..

The RRC has issued one drilling permit (amended twice), issued January 13, 2009, permitted to 18,500 ft.

It was permitted by Range Production Company and has since transferred to Bbx Operating L.L.C. on the wellbore schedule.

Completion filings report 4 formation tops, including Austin Chalk, Pettit, Knowles, Bossier.

Operator of record

BBX Operating L.L.C.

Permitted by Range Production Company; the EWA schedule now lists a different operator.

San Antonio, TX · P-5 Y, filed Nov 4, 2025 · 120 permits on file · (281) 414-3120

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBBX Operating L.L.C.
Production reportsRange Production Companythrough Sep 2012
Latest permitRange Production CompanyApr 6, 2009

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

18,500
total depth, ft
3
permits on file
Apr 6, 2009
last permit issued
Sep 1, 2009
completed
0
cumulative oil, bbl
126K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2009 THROUGH Mar 2025

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 1, 2009
Shut in
—
Plugged
Nov 18, 2024

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Flournoy, Ruby G-6-256201Manning (Bossier Sand)BBX Operating, L.L.C.10126KAug 2009 – Mar 2025

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Range Production CompanyAug 2009 → Sep 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
677145-97DrillRange Production CompanyApr 6, 2009Apr 6, 2009Jan 31, 200918,500
677145-98DrillRange Production CompanyMar 9, 2009Jan 13, 2009Jan 31, 200918,000
677145-99DrillRange Production CompanyJan 8, 2009Jan 13, 2009Jan 31, 200918,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-256201————

Formation tops

As filed on W-2/G-1. Subsea from 284 ft elevation.Download CSV →

FormationMD ftSubsea
Austin ChalkAUSTIN8,504-8,220
Pettit11,962-11,678
Knowles15,232-14,948
Bossier16,096-15,812

Perforations

Perforated and open-hole intervals.

FromToType
17,24017,260Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.753,35614.752,230 S
514,7906.5285 S
7.87515,2909.8751,000 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jul 12, 2010Oct 30, 2009Yes
00Jun 15, 2010——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/00530383, documented in the API reference.