WELL · 42-311-34095 · DISTRICT 1

Quintanilla, Paloma Horton #6

N

McMullen County  · Vertical

Quintanilla, Paloma Horton #6 (API 42-311-34095) is a permitted well in Mcmullen County filed by Welhausen Operating Company, LP; no completion report is on file yet.

The RRC has issued 2 drilling permits between 2004 and 2008, permitted to 11,000 ft.

Completion filings report 2 formation tops, including Carrizo, Olmos.

Its lease has reported 325K barrels of oil and 680K mcf of gas since May 2001, last reporting in July 2026. The lease carries 5 wells, so these are lease totals, not this well alone.

Operator of record

Welhausen Operating Company, LP

Beeville, TX · P-5 Y, filed Jul 7, 2017 · 98 permits on file · (361) 362-4560

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsGTG Operating, LLCthrough Feb 2026
Latest permitWelhausen Operating Company, LPSep 15, 2008
11,000
total depth, ft
2
permits on file
Sep 15, 2008
last permit issued
—
completed
325K
cumulative oil, bbl
680K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2001 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Paloma-Horton Quintanilla O-1-14345A.W.P. (Olmos)GTG Operating, LLC5325K680KMay 2001 – Jul 2026

Oil, barrels lease total

Last 12 months 931 · prior 12 2,737(-66%)

0200400202420252026

Gas, mcf lease total

Last 12 months 299 · prior 12 3,787(-92%)

05001K202420252026

Chain of custody

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

  1. 1Welhausen Operating Co., Inc.May 2001 → Oct 2001
  2. 2Welhausen Operating Company, LPNov 2001 → Dec 2011
  3. 3Layline Petroleum I, LLCJan 2012 → May 2013
  4. 4Wapiti Operating, LLCJun 2013 → Mar 2015
  5. 5Clearly Petroleum, LLCApr 2015 → Apr 2020
  6. 6GTG Operating, LLCMay 2020 → Feb 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
666329-99DrillWelhausen Operating Company, LPJul 9, 2008Sep 15, 2008Dec 7, 200811,000
552293-99DrillWelhausen Operating Company, LPOct 14, 2004Oct 18, 2004—9,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-14345————

Formation tops

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

FormationMD ftSubsea
Carrizo4,330-4,038
Olmos9,274-8,982

Perforations

Perforated and open-hole intervals.

FromToType
9,2769,296Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,348——
9.6251,51212.25495 S
4.59,5797.8751,440 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
00Aug 27, 2009Apr 8, 2009Yes
00Jul 28, 2009——

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