TEXAS · WELLS · ECTOR COUNTY · GARDENDALE 14 LEASE · API 42-135-41056 · DISTRICT 7B

Gardendale 14 #6

Shut in

Ector County · Spraberry (Trend Area) field · Shut In  · Vertical

Gardendale 14 #6 (API 42-135-41056) is a well in Ector County operated by Ovintiv USA Inc., completed January 7, 2013 and listed as shut in on the RRC schedule, shut in March 1, 2026.

The RRC has issued one drilling permit (amended once), issued May 2, 2011, permitted to 11,655 ft.

It was permitted by Berry Oil Comp. and has since transferred to Ovintiv USA Inc. on the wellbore schedule.

Completion filings report 6 formation tops, including Yates, San Andres, Clear Fork, Spraberry.

Its lease has reported 886K barrels of oil and 2.88M mcf of gas since March 2010, last reporting volume in April 2026. The lease carries 15 wells, so these are lease totals, not this well alone.

Operator of record

Ovintiv USA Inc.

Permitted by Berry Oil Comp.; the EWA schedule now lists a different operator.

Based in
Denver, CO
P-5 status
Active (A)
P-5 last filed
Dec 12, 2025
Permits on file
1,391
Phone
(720) 876-5176

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOvintiv USA Inc.
Production reportsOvintiv USA Inc.through Apr 2026
Latest permitBerry Oil Comp.May 2, 2011

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

11,655
total depth, ft
2
permits on file
May 2, 2011
last permit issued
Jan 7, 2013
completed
886K
cumulative oil, bbl
2.88M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2010 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 7, 2013
Shut in
Mar 1, 2026
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 15 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Gardendale 14 O-10-41018Spraberry (Trend Area)Ovintiv USA Inc.15886K2.88MMar 2010 – Apr 2026

Oil, barrels lease total

Last 12 months 20,005 · prior 12 22,472(-11%)

01K2K3K202420252026

Gas, mcf lease total

Last 12 months 35,835 · prior 12 65,120(-45%)

05K10K15K202420252026

Chain of custody

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

  1. 1Berry Oil Comp.Apr 2010 → Jun 2014
  2. 2Linn Operating, Inc.Jul 2014 → Feb 2015
  3. 3FDL Operating, LLCMar 2015 → Dec 2021
  4. 4Contango Resources, LLCJan 2022 → Nov 2022
  5. 5Slant Operating, LLCDec 2022 → May 2023
  6. 6Ovintiv USA Inc.Jun 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
715164-98DrillBerry Oil Comp.Dec 2, 2011May 2, 2011Mar 26, 201211,900
715164-99DrillBerry Oil Comp.Apr 27, 2011May 2, 2011—11,900

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 7, 2013Gardendale 14 O-10-41018Spraberry (Trend Area)Ovintiv USA Inc.Shut In · shut in Mar 1, 202611,655

Formation tops

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

FormationMD ftSubsea
Yates3,100-161
San Andres4,905-1,966
Clear ForkCLEARFORK7,318-4,379
Spraberry8,110-5,171
Dean9,364-6,425
Strawn10,544-7,605

Perforations

Perforated and open-hole intervals.

FromToType
9,19511,480Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37541917.5375 S
8.6255,40011850 S
5.511,6557.8751,028 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 1, 2013Jul 10, 2013—
00Sep 4, 2013Sep 29, 2012Yes

Well logs

2 logs loaded from the RRC's log index, the latest received May 8, 2015. Density, Neutron, 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
NEUTRON/DENSITY POROSITYSpans Yates, San Andres, Clear Fork, Spraberry, Dean, StrawnTIFF4,500 to 11,579May 8, 2015run Apr 13, 20128.24
COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYSpans Yates, San Andres, Clear Fork, Spraberry, Dean, StrawnTIFF200 to 11,601May 6, 2015run Apr 10, 20121.63

"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. The University Lands library has no per-well link: then paste it into its 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/13541056, documented in the API reference.