WELL · 42-165-36600 · DISTRICT 8
Hollingsworth #10D
Gaines County · Flanagan (Clearfork Cons.) field · Producing · Vertical
Hollingsworth #10D (API 42-165-36600) is a well in Gaines County operated by Kimbell Operating Company, completed October 13, 2006 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued June 26, 2006, permitted to 6,750 ft.
Its lease has reported 114K barrels of oil and 18K mcf of gas since October 2006, last reporting in July 2026.
Operator of record
Fort Worth, TX · P-5 Y, filed Mar 4, 2026 · 9 permits on file · (214) 725-5777
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Kimbell Operating Company |
| Production reports | Kimbell Operating Companythrough Apr 2026 |
| Latest permit | Kimbell Operating CompanyJun 26, 2006 |
- 6,750
- total depth, ft
- 1
- permits on file
- Jun 26, 2006
- last permit issued
- Oct 13, 2006
- completed
- 114K
- cumulative oil, bbl
- 18K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 2006 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Oct 13, 2006
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Hollingsworth O-11-69003 | Flanagan (Clearfork, Cons.) | Kimbell Operating Company | 1 | 114K | 18K | Oct 2006 – Jul 2026 |
Oil, barrels lease total
Last 12 months 2,850 · prior 12 3,962(-28%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Kimbell Operating CompanyOct 2006 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 621513-99 | Drill | Kimbell Operating Company | Jun 23, 2006 | Jun 26, 2006 | Jul 18, 2006 | 6,750 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-11-69003 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,255 | 6,260 | Perforated |
| 6,273 | 6,275 | Perforated |
| 6,300 | 6,305 | Perforated |
| 6,360 | 6,365 | Perforated |
| 6,392 | 6,397 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,810 | 11 | 605 S |
| 5.5 | 6,713 | 7.875 | 1,200 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Mar 1, 2007 | Oct 30, 2006 | Yes |
| 00 | Nov 3, 2006 | — | — |
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.
- Wellbore filings for 42-165-36600 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-165-36600 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. 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/16536600, documented in the API reference.