TEXAS · WELLS · ECTOR COUNTY · TXL NORTH UNIT LEASE · API 42-135-39556 · DISTRICT 7B

TXL North Unit #1009

Y

Ector County · TXL (Tubb) field · Producing  · Vertical

Txl North Unit #1009 (API 42-135-39556) is a well in Ector County operated by Formentera Operations LLC, completed November 5, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued July 8, 2008, permitted to 6,890 ft.

It was permitted by Apache Corporation and has since transferred to Formentera Operations LLC on the wellbore schedule.

Completion filings report 8 formation tops, including Yates, Queen, Grayburg, San Andres.

Its lease has reported 13.9M barrels of oil and 40.3M mcf of gas since January 1993, last reporting volume in April 2026. The lease carries 496 wells, so these are lease totals, not this well alone.

Operator of record

Formentera Operations LLC

Permitted by Apache Corporation; the EWA schedule now lists a different operator.

Based in
Austin, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jun 11, 2026
Permits on file
93
Phone
(512) 514-5779

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFormentera Operations LLC
Production reportsFormentera Operations LLCthrough Apr 2026
Latest permitApache CorporationJul 8, 2008

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

6,890
total depth, ft
1
permits on file
Jul 8, 2008
last permit issued
Nov 5, 2009
completed
13.9M
cumulative oil, bbl
40.3M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 5, 2009
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.

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
TXL North Unit O-10-20487TXL (Tubb)Formentera Operations LLC49613.9M40.3MJan 1993 – Apr 2026

Oil, barrels lease total

Last 12 months 91,054 · prior 12 102,642(-11%)

05K10K15K202420252026

Gas, mcf lease total

Last 12 months 257,591 · prior 12 276,773(-7%)

010K20K30K202420252026

Chain of custody

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

  1. 1Shell Western E&P Inc.Jan 1993 → Nov 1995
  2. 2Anadarko Petroleum CorporationDec 1995 → Mar 2007
  3. 3Apache CorporationApr 2007 → Jun 2021
  4. 4Slant Operating, LLCJul 2021 → Oct 2023
  5. 5Formentera Operations LLCNov 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
664797-99DrillApache CorporationJun 18, 2008Jul 8, 2008Sep 11, 20089,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Nov 5, 2009TXL North Unit O-10-20487TXL (Tubb)Formentera Operations LLCProducing6,890

Formation tops

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

FormationMD ftSubsea
Yates2,710583
Queen3,473-180
Grayburg3,809-516
San Andres4,031-738
Glorieta5,208-1,915
Clear ForkCLEARFORK5,418-2,125
Tubb5,967-2,674
Wichita-AlbanyWICHITA6,479-3,186

Perforations

Perforated and open-hole intervals.

FromToType
5,9075,995Perforated
6,1406,336Perforated
6,5486,714Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,47512.25750 S
5.56,8907.875900 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
00Apr 28, 2010Nov 12, 2009—
00Jan 10, 2009Oct 28, 2008Yes
00Dec 12, 2008——

Well logs

2 logs loaded from the RRC's log index, the latest received Sep 26, 2011. Cased hole, Density, Neutron. 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, Queen, Grayburg, San Andres, Glorieta, Clear Fork, Tubb, Wichita-AlbanyTIFF200 to 6,880Sep 26, 2011run Sep 19, 20082.86
SURVEYS CASED HOLESpans San Andres, Glorieta, Clear Fork, Tubb, Wichita-AlbanyTIFF5,000 to 6,805Sep 26, 2011run Sep 19, 20084.76

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