WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-439-36622

Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof API 42-439-36622Clear

Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.

26 LOG FILES ON 17 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Bruder Buckeye #3HHZ42-439-37265Tarrant, TX · TEP Barnett USA LLChereGamma RayLAS + TIFF0 to 14,558Jul 28, 2026
Buckeye Tree Mipa #2HHZ42-439-37296Tarrant, TX · TEP Barnett USA LLChereGamma RayLAS + TIFF0 to 20,006Jun 30, 2026
Pleasant Ridge #3HHZ42-439-37253Tarrant, TX · TEP Barnett USA LLChereGamma RayLAS + TIFF0 to 13,292Apr 23, 2026
Captain America Mipa #5HHZ42-439-37297Tarrant, TX · TEP Barnett USA LLChereGamma RayLAS + TIFF0 to 20,210Jun 30, 2026
Captain el Dorado Mipa #3HHZ42-439-37298Tarrant, TX · TEP Barnett USA LLChereGamma RayLAS + TIFF1,630 to 20,302Sep 24, 2026
Bruder-Watson #2HHZ42-439-37254Tarrant, TX · TEP Barnett USA LLChereGamma RayLAS + TIFF0 to 15,355Apr 23, 2026
Planet Zero Mipa #4HHZ42-439-37301Tarrant, TX · TEP Barnett USA LLChereGamma RayLAS + TIFF1,665 to 18,517Aug 26, 2026
Planet Earth Mipa #3HHZ42-439-37302Tarrant, TX · TEP Barnett USA LLChereGamma RayLAS + TIFF0 to 20,986Aug 26, 2026
DWG Unit #8HHZ42-439-36705Tarrant, TX · BKV North Texas LLC0.77RESISTIVITYTIFF5,000 to 14,554Jul 13, 2015run Oct 24, 2013
DWG Unit #1HHZ42-439-35147Tarrant, TX · BKV North Texas LLC1.00SURVEYS CASED HOLETIFF6,100 to 14,683Mar 22, 2011run Aug 26, 2010
Bruder-Watson #1HHZ42-439-34948Tarrant, TX · TEP Barnett USA LLC1.10NEUTRON/DENSITY POROSITYTIFF7,690 to 12,987Oct 8, 2013run Sep 14, 2010
Bruder-Watson #1HHZ42-439-34948Tarrant, TX · TEP Barnett USA LLC1.10RESISTIVITYTIFF1,626 to 12,987Oct 8, 2013run Sep 14, 2010
DWG Unit #2HHZ42-439-35329Tarrant, TX · BKV North Texas LLC1.14SURVEYS CASED HOLETIFF6,100 to 12,950Mar 22, 2011run Sep 24, 2010
Veteran B Unit #1HHZ42-439-34643Tarrant, TX · BKV North Texas LLC1.24RESISTIVITYTIFF6,270 to 8,695Feb 6, 2013run Jan 10, 2010
Elkins Unit #2HHZ42-439-35336Tarrant, TX · BKV North Texas LLC1.33SURVEYS CASED HOLETIFF5,600 to 13,162Aug 1, 2011run Oct 29, 2010
Elkins Unit #1HHZ42-439-34282Tarrant, TX · BKV North Texas LLC1.60SURVEYS CASED HOLETIFF5,950 to 11,945May 11, 2010
Elkins Unit #10HHZ42-439-36676Tarrant, TX · BKV North Texas LLC1.78RESISTIVITYTIFF5,000 to 12,008Apr 29, 2015run Oct 5, 2013
Veteran a Unit #1HHZ42-439-34642Tarrant, TX · BKV North Texas LLC1.85SURVEYS CASED HOLETIFF5,940 to 10,684May 11, 2010run Dec 29, 2009

About this data

Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. 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. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.

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