WELL · 42-237-38985 · DISTRICT 9
Hanna #2
Jack County · Franklin (Strawn) field · Vertical
Hanna #2 (API 42-237-38985) is a plugged well in Jack County, plugged July 6, 2017, last operated by Breck Operating Corp..
The RRC has issued one drilling permit, issued September 29, 2006, permitted to 5,500 ft.
Completion filings report one formation top, including Strawn.
Its lease has reported 3.57K barrels of oil and 17.2K mcf of gas since April 2007, last reporting in September 2017.
Operator of record
Breckenridge, TX · P-5 Y, filed Mar 8, 2019 · 295 permits on file · (254) 559-0881
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Breck Operating Corp. |
| Production reports | Breck Operating Corp.through Dec 2015 |
| Latest permit | Breck Operating Corp.Sep 29, 2006 |
- 5,500
- total depth, ft
- 1
- permits on file
- Sep 29, 2006
- last permit issued
- Apr 11, 2007
- completed
- 3.57K
- cumulative oil, bbl
- 17.2K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2007 THROUGH Sep 2017
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Apr 11, 2007
- Shut in
- —
- Plugged
- Jul 6, 2017
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 |
|---|---|---|---|---|---|---|
| Hanna O-13-30854 | Franklin (Strawn) | Breck Operating Corp. | 1 | 3.57K | 17.2K | Apr 2007 – Sep 2017 |
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.
- 1Breck Operating Corp.Sep 2007 → Sep 2015
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 626310-99 | Drill | Breck Operating Corp. | Sep 20, 2006 | Sep 29, 2006 | Oct 30, 2006 | 5,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-30854 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,031 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Strawn | 3,386 | -2,355 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,386 | 3,412 | Perforated |
| 3,424 | 3,445 | Perforated |
| 3,452 | 34,796 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,308 | 12.25 | 615 S |
| 5.5 | 3,640 | 7.875 | 360 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 | Oct 30, 2007 | Sep 21, 2007 | Yes |
| 00 | Oct 26, 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-237-38985 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-237-38985 → 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/23738985, documented in the API reference.