WELL · 42-363-34073 · DISTRICT 7

Trull A #2

Plugged

Palo Pinto County · Musgrove (Conglomerate) field  · Vertical

Trull A #2 (API 42-363-34073) is a plugged well in Palo Pinto County, plugged March 6, 2013, last operated by Borderline Operating Corp..

The RRC has issued one drilling permit, issued March 7, 1991, permitted to 4,999 ft.

It was permitted by K & M Exploration, 1973-3 Ltd. and has since transferred to Borderline Operating Corp. on the wellbore schedule.

Completion filings report 4 formation tops, including Strawn, Conglomerate, Marble Falls, Ellenburger.

Operator of record

Borderline Operating Corp.

Permitted by K & M Exploration, 1973-3 Ltd.; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed Dec 4, 2025 · 98 permits on file · (940) 550-4900

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBorderline Operating Corp.
Production reportsBorderline Operating Corp.through Mar 2012
Latest permitK & M Exploration, 1973-3 Ltd.Mar 7, 1991

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

4,999
total depth, ft
1
permits on file
Mar 7, 1991
last permit issued
May 2, 1991
completed
0
cumulative oil, bbl
33.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2013

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 2, 1991
Shut in
—
Plugged
Mar 6, 2013

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
Trull "A" G-8-138753Musgrove (Conglomerate)Borderline Operating Corp.1033.1KJan 1993 – Mar 2013

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1K & M Exploration, 1973-3 Ltd.Dec 1994 → Jan 1995
  2. 2Kendrick Oil and Gas CompanyMay 2001 → Feb 2012
  3. 3Borderline Operating Corp.Mar 2012 → Mar 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
385241-99DrillK & M Exploration, 1973-3 Ltd.Mar 1, 1991Mar 7, 1991Mar 14, 19914,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-138753————

Formation tops

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

FormationMD ftSubsea
Strawn2,246-1,355
Conglomerate3,926-3,035
Marble Falls4,325-3,434
Ellenburger4,648-3,757

Perforations

Perforated and open-hole intervals.

FromToType
3,9964,004Perforated
4,5304,600Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62539512.25240 S
5.54,4097.875150 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
00Nov 14, 2012Jul 27, 2012—
00Jul 30, 1991Jul 16, 1991Yes
00Jul 29, 1991——

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