TEXAS · WELLS · WICHITA COUNTY · RIO BRAVO "ACE" LEASE · API 42-485-44372 · DISTRICT 7C

Rio Bravo Ace #E 28

On schedule

Wichita County · Wichita County (Special) field · Producing  · Vertical

Rio Bravo Ace #E 28 (API 42-485-44372) is a well in Wichita County operated by Newport Operating LLC, completed May 19, 2008 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 31, 2008, permitted to 2,392 ft.

It was permitted by Extex Operating Company and has since transferred to Newport Operating LLC on the wellbore schedule.

Completion filings report 5 formation tops, including Coleman Junction, Saddle Creek, Dyson Lime, Megargel Lime.

Its lease has reported 159K barrels of oil since June 2007, last reporting volume in August 2026. The lease carries 16 wells, so these are lease totals, not this well alone.

Operator of record

Newport Operating LLC

Permitted by Extex Operating Company; the EWA schedule now lists a different operator.

Based in
Burkburnett, TX
P-5 status
Active (A)
P-5 last filed
Mar 6, 2026
Permits on file
193
Phone
(972) 439-6094

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleNewport Operating LLC
Production reportsNewport Operating, LLCthrough Apr 2026
Latest permitExtex Operating CompanyMar 31, 2008

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

2,392
total depth, ft
1
permits on file
Mar 31, 2008
last permit issued
May 19, 2008
completed
159K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · JUN 2007 THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 19, 2008
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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 16 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Rio Bravo "Ace" O-13-31066Wichita County (Special)Newport Operating, LLC16159K0Jun 2007 – Aug 2026

Oil, barrels lease total

Last 12 months 2,452 · prior 12 3,631(-32%)

0200400202420252026

Wells named Rio Bravo Ace

Newport Operating LLC's other wells filed under this lease name in Wichita County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Rover Operating Company, LLCJun 2007 → Nov 2025
  2. 2Extex Operating CompanyOct 2007 → May 2009
  3. 3Newport Operating, LLCDec 2025 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
657631-99DrillExtex Operating CompanyMar 18, 2008Mar 31, 2008Apr 17, 20082,400

Completions

CompletedLeaseFieldOperatorStatusDepth
May 19, 2008Rio Bravo Ace O-13-31066Wichita County (Special)Newport Operating LLCProducing2,392

Formation tops

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

FormationMD ftSubsea
Coleman Junction674460
Saddle CreekSADDLE CREEK LIME1,267-133
Dyson Lime1,657-523
Megargel Lime1,814-680
Gunsite Sand1,918-784

Perforations

Perforated and open-hole intervals.

FromToType
7141,043Perforated
1,3291,442Perforated
1,6621,922Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6256112.2550 S
5.52,0627.875425 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 →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Nov 5, 2008Jun 9, 2008Yes
00Oct 23, 2008——

Well logs

1 log loaded from the RRC's log index, the latest received Nov 21, 2008. 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 describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Coleman Junction, Saddle Creek, Dyson Lime, Megargel Lime, Gunsite SandTIFF60 to 2,390Nov 21, 2008run Apr 19, 20081.70

"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.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

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