WELL · 42-267-00049 · DISTRICT 7
Crawford A #1
Kimble County · Crawford (Strawn Lime) field · Vertical
Crawford A #1 (API 42-267-00049) is a plugged well in Kimble County, plugged February 15, 1996, last operated by Mcdonald Bruce.
The RRC has issued one drilling permit, issued February 27, 1990, permitted to 2,400 ft.
It was permitted by Mcdonald/Northington and has since transferred to Mcdonald Bruce on the wellbore schedule.
Completion filings report one formation top, including Ellenburger.
Operator of record
Permitted by McDonald/Northington; the EWA schedule now lists a different operator.
George West, TX · P-5 Y, filed Jul 3, 1996 · 3 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | McDonald Bruce |
| Production reports | none |
| Latest permit | McDonald/NorthingtonFeb 27, 1990 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 2,400
- total depth, ft
- 1
- permits on file
- Feb 27, 1990
- last permit issued
- Mar 7, 1990
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Feb 1996
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Mar 7, 1990
- Shut in
- —
- Plugged
- Feb 15, 1996
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 "A" G-9-138455 | Crawford (Strawn Lime) | McDonald, Bruce | 1 | 0 | 0 | Jan 1993 – Feb 1996 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 370063-99 | Reenter | McDonald/Northington | Feb 20, 1990 | Feb 27, 1990 | Oct 2, 1989 | 2,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-9-138455 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,240 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Ellenburger | 2,372 | -132 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,356 | 2,405 | Open hole |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 420 | 17.5 | 400 S |
| 8.625 | 2,352 | 11 | 150 S |
| 4.5 | 2,356 | 8 | 150 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 | Aug 16, 1991 | Jun 5, 1991 | Yes |
| 00 | Jun 28, 1991 | — | — |
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-267-00049 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-267-00049 → 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/26700049, documented in the API reference.