WELL · 42-485-44981 · DISTRICT 9

Burns C #4

Y

Wichita County · Wichita County Regular field · Shut IN  · Vertical

Burns C #4 (API 42-485-44981) is a well in Wichita County operated by R2q Operating LLC, completed January 24, 2011 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued November 24, 2010, permitted to 1,999 ft.

It was permitted by Bto Venture, Inc. and has since transferred to R2q Operating LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Tannehill, Cisco.

Its lease has reported 10.7K barrels of oil and 21 mcf of gas since January 1993, last reporting in July 2026. The lease carries 7 wells, so these are lease totals, not this well alone.

Operator of record

R2Q Operating LLC

Permitted by Bto Venture, Inc.; the EWA schedule now lists a different operator.

Iowa Park, TX · P-5 Y, filed Jul 4, 2026 · 38 permits on file · (940) 733-8152

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleR2Q Operating LLC
Production reportsR2Q Operating LLCthrough Oct 2023
Latest permitBto Venture, Inc.Nov 24, 2010

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

1,999
total depth, ft
1
permits on file
Nov 24, 2010
last permit issued
Jan 24, 2011
completed
10.7K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 24, 2011
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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 7 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Burns C O-13-28416Wichita County RegularR2Q Operating LLC710.7K21Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 0 · prior 12 0

050100202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Bto Venture, Inc.Jan 1993 → Nov 2012
  2. 2Urban Oil & Gas Group, LLCDec 2012 → Aug 2021
  3. 3R2Q Operating LLCMar 2022 → Oct 2023

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
705464-99DrillBto Venture, Inc.Nov 16, 2010Nov 24, 2010Dec 2, 20101,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-28416————

Formation tops

As filed on W-2/G-1. Subsea from 1,002 ft elevation.Download CSV →

FormationMD ftSubsea
TannehillTANNEHILL SAND681321
CiscoCISCO SAND1,036-34

Perforations

Perforated and open-hole intervals.

FromToType
1,0361,040Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,1366.75175 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Sep 28, 2011Feb 11, 2011Yes

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.

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/48544981, documented in the API reference.