WELL · 42-057-31723 · DISTRICT 2
Trull B #3
Calhoun County · Appling Deep (Frio) field · Directional
Trull B #3 (API 42-057-31723) is a plugged well in Calhoun County, plugged November 23, 2010, last operated by Brigham Oil & Gas L.P..
The RRC has issued one drilling permit, issued April 18, 2006, permitted to 13,000 ft.
Completion filings report 2 formation tops, including Miocene (undifferentiated), Frio.
Operator of record
Austin, TX · P-5 Y, filed Aug 7, 2015 · 288 permits on file · (512) 427-3300
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Brigham Oil & Gas L.P. |
| Production reports | Brigham Oil & Gas, L.P.through May 2009 |
| Latest permit | Brigham Oil & Gas, L.P.Apr 18, 2006 |
- 13,000
- total depth, ft
- 1
- permits on file
- Apr 18, 2006
- last permit issued
- Jun 13, 2006
- completed
- 0
- cumulative oil, bbl
- 78.5K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 2006 THROUGH Nov 2010
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 13, 2006
- Shut in
- —
- Plugged
- Nov 23, 2010
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Trull B G-2-226864 | Appling Deep (Frio) | Brigham Oil & Gas, L.P. | 1 | 0 | 78.5K | Jun 2006 – Nov 2010 |
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.
- 1Brigham Oil & Gas, L.P.Jun 2006 → May 2009
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 617722-99 | Drill | Brigham Oil & Gas, L.P. | Apr 17, 2006 | Apr 18, 2006 | Apr 23, 2006 | 13,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-226864 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 5 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,524 | 9,530 | Perforated |
| 9,640 | 9,643 | Perforated |
| 9,646 | 9,648 | Perforated |
| 11,949 | 11,953 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 2,640 | 14.75 | 1,965 S |
| 7.625 | 7,890 | 9.875 | 520 S |
| 4.5 | 12,727 | 6.5 | 840 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Sep 24, 2008 | May 14, 2008 | — |
| 00 | Jun 14, 2007 | Mar 30, 2007 | — |
| 00 | Jun 4, 2007 | Jul 31, 2006 | Yes |
| 00 | May 30, 2007 | — | — |
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.
- Wellbore filings for 42-057-31723 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-057-31723 → scanned completion filings
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/05731723, documented in the API reference.