WELL · 42-505-35984 · DISTRICT 4

Whittier #6

Y

Zapata County · Haynes (Middle Wilcox Cons.) field · Producing  · Directional

Whittier #6 (API 42-505-35984) is a well in Zapata County operated by Petrovybe Opco LLC, completed October 28, 2007 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued September 19, 2007, permitted to 15,000 ft.

It was permitted by Legend Natural Gas II, LP and has since transferred to Petrovybe Opco LLC on the wellbore schedule.

No lease production has been reported under this well’s leases.

Operator of record

Petrovybe Opco LLC

Permitted by Legend Natural Gas II, LP; the EWA schedule now lists a different operator.

Based in
Plano, TX
P-5 status
Active – Extension (X)
P-5 last filed
Dec 29, 2025
Permits on file
6
Phone
(214) 810-6207

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetrovybe Opco LLC
Production reportsPetrovybe Opco LLCthrough Apr 2026
Latest permitLegend Natural Gas II, LPJan 22, 2008

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

15,000
total depth, ft
2
permits on file
Jan 22, 2008
last permit issued
Oct 28, 2007
completed
0
cumulative oil, bbl
519K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 28, 2007
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Whittier G-4-250826Haynes (Middle Wilcox Cons.)Petrovybe Opco LLC10519KOct 2007 – Jul 2026

Gas, mcf lease total

Last 12 months 2,702 · prior 12 3,235(-16%)

05001K202420252026

Chain of custody

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

  1. 1Legend Natural Gas II, LPDec 2007 → Feb 2015
  2. 2Trinity River Energy Oper, LLCMar 2015 → Aug 2017
  3. 3Wagner Oil CompanyNov 2017 → Jan 2021
  4. 4Fletcher Operating, LLCFeb 2021 → Nov 2025
  5. 5Petrovybe Opco LLCDec 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
646157-98DrillLegend Natural Gas II, LPJan 11, 2008Jan 22, 2008Sep 30, 200715,000
646157-99DrillLegend Natural Gas II, LPSep 14, 2007Sep 19, 2007—15,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-250826————

Perforations

Perforated and open-hole intervals.

FromToType
10,81410,820Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62573312.25315 S
79,2908.75285 S
4.511,5006.25305 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
00Oct 29, 2009Mar 10, 2008Yes
00Sep 14, 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/50535984, documented in the API reference.