TEXAS · WELLS · GLASSCOCK COUNTY · EDMONDSON A LEASE · API 42-173-33215 · DISTRICT 7B
Edmondson A #1920
Glasscock County · Conger (Penn) field · Producing · Vertical
Edmondson A #1920 (API 42-173-33215) is a well in Glasscock County operated by Burk Royalty CO. Ltd., completed May 16, 2006 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued March 28, 2006, permitted to 8,783 ft.
It was permitted by Range Production Company and has since transferred to Burk Royalty CO. Ltd. on the wellbore schedule.
Completion filings report 3 formation tops, including San Andres, Cisco, Canyon.
Its lease has reported 877K barrels of oil and 13.2M mcf of gas since December 1993, last reporting volume in April 2026. The lease carries 37 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Range Production Company; the EWA schedule now lists a different operator.
- Based in
- Wichita Falls, TX
- P-5 status
- Active (A)
- P-5 last filed
- Dec 4, 2025
- Permits on file
- 384
- Phone
- (940) 397-8600
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Burk Royalty Co. Ltd. |
| Production reports | Burk Royalty Co., Ltd.through Apr 2026 |
| Latest permit | Range Production CompanyMar 28, 2006 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,783
- total depth, ft
- 1
- permits on file
- Mar 28, 2006
- last permit issued
- May 16, 2006
- completed
- 877K
- cumulative oil, bbl
- 13.2M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Dec 1993 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- May 16, 2006
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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; they carry 37 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Edmondson A O-10-34061 | Conger (Penn) | Burk Royalty Co., Ltd. | 37 | 877K | 13.2M | Dec 1993 – Apr 2026 |
Gas, mcf lease total
Last 12 months 111,439 · prior 12 117,948(-6%)
Oil, barrels lease total
Last 12 months 2,974 · prior 12 3,185(-7%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Wagner & Brown, Ltd.Dec 1993 → Dec 2003
- 2Range Production CompanyJan 2004 → Jul 2014
- 3EQT Production Texas, LLCAug 2014 → Jun 2018
- 4Stanolind Production LLCJul 2018 → Dec 2020
- 5Slant Operating, LLCJan 2021 → Dec 2021
- 6Burk Royalty Co., Ltd.Jan 2022 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 616552-99 | Drill | Range Production Company | Mar 28, 2006 | Mar 28, 2006 | Apr 23, 2006 | 9,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| May 16, 2006 | Edmondson A O-10-34061 | Conger (Penn) | Burk Royalty Co. Ltd. | Producing | 8,783 |
Formation tops
As filed on W-2/G-1. Subsea from 2,552 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| San Andres | 2,264 | 288 |
| Cisco | 8,124 | -5,572 |
| Canyon | 8,414 | -5,862 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,156 | 8,468 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 2,087 | 11.25 | 1,600 S |
| 5.5 | 8,783 | 7.875 | 875 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Dec 27, 2006 | May 26, 2006 | Yes |
| 00 | Aug 11, 2006 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received May 22, 2009. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITYSpans San Andres, Cisco, Canyon | TIFF | 200 to 8,750 | May 22, 2009run May 3, 2006 | 3.45 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-173-33215 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-173-33215 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/17333215, documented in the API reference.