WELL · 42-133-37365 · DISTRICT 7
Crawford B #2SW
Eastland County · Vertical
Crawford B #2SW (API 42-133-37365) is a plugged well in Eastland County, plugged June 1, 1989, last operated by Kornye-Tillman Company.
The RRC has issued 2 drilling permits between 1989 and 2008, permitted to 5,100 ft.
It holds an active disposal or injection permit.
Operator of record
Cleburne, TX · P-5 Y, filed Oct 4, 2025 · 34 permits on file · (817) 832-4338
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Kornye-Tillman CompanyAug 27, 2008 |
- 5,100
- total depth, ft
- 2
- permits on file
- Aug 27, 2008
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Nov 2008 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Jun 1, 1989
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 |
|---|---|---|---|---|---|---|
| Crawford B G-8-244086 | Eastland County Regular (Gas) | Blackbird R 22 OG L.L.C. | 1 | 0 | 0 | Nov 2008 – Jul 2026 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 668549-99 | Reenter | Kornye-Tillman Company | Aug 7, 2008 | Aug 27, 2008 | Oct 19, 2008 | 5,100 |
| 358549-99 | Drill | Hayes Oil & Gas Co. | Apr 24, 1989 | Apr 24, 1989 | May 24, 1989 | 5,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-244086 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,590 | 4,640 | Perforated |
| 4,700 | 4,790 | Perforated |
| 4,860 | 4,890 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 102 | 11 | 70 S |
| 5.5 | 4,952 | 7.875 | 250 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 | Feb 23, 2009 | Dec 18, 2008 | — |
| 00 | Jan 21, 2009 | — | — |
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-133-37365 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-133-37365 → 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.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 0
- bbl, last 12 reported months
- 232K
- bbl, all reported
- Jan 2025
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000099059 | W-14 Disposal | Active | 10,000 | 2,125 | 4,250–5,000 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 0 · prior 12 0
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/13337365, documented in the API reference.