OPERATORS · TEXAS · P-5 NUMBER 257084

Expro Engineering Co.

P-5 status
Inactive (I)
P-5 last filed
Nov 25, 1986
Based in
Fort Worth, TX

Petrora groups this registration with Expro Engineering, Inc., Texas (7 active wells). Expro Engineering, Inc. across every state →

Expro Engineering CO. has filed no drilling permits in the past 12 months; its most recent permit was issued July 11, 1986.

The RRC wellbore file lists 2 wells under its operatorship.

3 drilling permits have been issued to this operator number since 1986; its P-5 organization report was last filed November 25, 1986.

0
permits, last 12 months
—
vs prior 12 months (0)
0
counties, 12 months
0
producing wells, of 2 of record
0
leases it reports
—
horizontal, 12 months

WINDOWS ON THE RRC ISSUE DATE · COMPUTED NOV 5, 2026

Permits issued by month

LAST 60 MONTHS · BY ISSUE DATE

Last 12 months 0 · prior 12 0

0120222023202420252026

Counties

Counties by permits in the last 12 months, with all-time permits and current wells of record there.

County12 moAll timeWellsLast
Stephens county →—30Jul 11, 1986

All 3 permits, searchable → · Leases it reports → · On the map →

Formations in its completed wells

Tops reported on completion filings for wells it operates. RRC wellbore file. About tops →

FormationWellsPermitted last 3 yrs
Mississippian10
Caddo10

Production by month

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Barrels on leases where this operator filed the production report. Lease-level by design; the latest months are revised upward as late reports arrive. How production is reported →

0
bbl oil, last 12 reported months
—
vs the 12 months before
0
mcf gas incl. casinghead, last 12
0
bbl oil since reporting began

No lease production reported under this operator number in the last ten years.

Beyond the permit record

RRC wellbore file

Wells of record

2
in the wellbore file
0
producing
0
shut in
0
injection
0
temp. abandoned
2
plugged

How it got them

0
permitted itself
2
acquired from others
0
permitted, now run by others

Each count opens the wells it counts. Acquired means the well's permit names a different operator than the schedule does today; wells it permitted that others now run are in its permit history, marked with who runs them now. Transfers and operator numbers →

Permit types

Last 12 months against the prior 12, and all time. A type opens the permit history filtered to it. What the types mean →

Type12 moPrior 12All time
Drill003

Fields

RRC regulatory fields with the most wells of record under this operator. The field opens its page; the count opens this operator's wells in it.

FieldWellsProducing
Alta Mesa N. (1850)200244410
Archer County Regular344600110

P-5 organization report

As registered with the RRC. About the P-5 →

Registration
Status Inactive (I)
Last filed Nov 25, 1986
Address
3220 N. Freeway, Ste. 120
Fort Worth, TX 76111
(817) 624-8425
Officers and agents
Eskew, Jerry · Partner
Browning, Dennis W. · Partner
Tettleton, Mark L. · Partner

Latest permits

NEWEST FIRST BY ISSUE DATE · FILED OR ON WELLS IT NOW OPERATES

PermitSeenIssuedOperatorCountyLease / wellDepthAPI
304062Jul 11, 1986Jul 11, 1986Expro Engineering Co.StephensWoods Heirs #14,60042934753
304062Jul 11, 1986Jul 11, 1986Expro Engineering Co.StephensWoods Heirs #14,60042934753
304056Jul 11, 1986Jul 11, 1986Expro Engineering Co.StephensWoods Heirs #14,60042934753
299556Mar 13, 1986Mar 13, 1986Amoco Production CompanyBrooksMestena Oil & Gas Company #25,70704730045
218355Oct 24, 1983Oct 24, 1983Enterprise Energy CorporationArcherBerend, J. #15,33700900033

Full permit history →

About this data

Registration from the RRC P-5 organization report, refreshed weekly. Permits from the OGA049M master and daily daf420 files; wells of record from the EWA wellbore schedule; production from PDQ lease reports by the operator that filed them, through the statewide reported-through month; disposal from UIC permits and H-10 reports. Summary figures are rebuilt nightly. Nothing is estimated.

Developers: this page as JSON is GET /v1/data/operators/tx/257084, documented in the API reference.