Ruth Evelyn (Cooper) Hovencamp was probably born on 22 Feb 1928 in Sussex Co., New Jersey, the daughter of Harry Clark Cooper and Ella M. (Crowell) Cooper. She married twice: Herbert L Hovencamp Sr (1946) and William D Mendoza (1970). She died in 2003 and was buried at Beemerville Cemetery, Beemerville, Sussex Co., New Jersey. One child is recorded.
Still unknown, and where we have looked
Searches recorded
state index 2026-10-22 · HER DAUGHTER'S GIVEN NAME. [J.575] gave the daughter only as 'Mrs. Robert Dougherty, of Newton'. Surname-only sweep of the New Jersey...
Searched for: HER DAUGHTER'S GIVEN NAME. [J.575] gave the daughter only as 'Mrs. Robert Dougherty, of Newton'. Surname-only sweep of the New Jersey BRIDE index, coll. 61253, ?name=_Hovencamp&count=50 - every Hovencamp bride in the state, 1901-2016, 34 ROWS, ALL READ - looking for the one who married a Dougherty.
Result: EXACTLY ONE: DIANA HOVENCAMP x ROBERT DOUGHERTY, Sep 1964, SUSSEX BOROUGH, certificate 34216 ->
[C.169]. Six months before the dinner notice, in her mother's own borough. She is now Living; her husband
Robert Dougherty. THE SWEEP SHAPE IS WHY IT WORKED: a given-name search was impossible - the catalog did not know her given name, which was the whole question - so the only usable instrument was the surname, read exhaustively. 34 rows is small enough to read, which is what made the surname-only recipe applicable here. WORTH KEEPING: Sussex Co. is thick with Hovencamps - the same 34 rows include June, Rodney, Wilbur, Gloria, Mary E, Mary A, Wayne, Dean, Alice and Wanda - so 'a Diana Hovencamp married a Dougherty' would NOT have been enough alone. The newspaper sentence is what tied that bride to this mother.
genealogybank 2026-10-22 · RE-RUN SIGNED IN, after the maintainer logged in - the earlier pass this day was recorded as NOT RUN, not as a null, and this is why...
Searched for: RE-RUN SIGNED IN, after the maintainer logged in - the earlier pass this day was recorded as NOT RUN, not as a null, and this is why that mattered. New Jersey, lname=Hovencamp&fname=Ruth, in BOTH collections: Obituaries, and NEWSPAPER ARCHIVES, which is a separate collection the result page exposes as a count. Also ran Ruth Mendoza in New Jersey obituaries.
Result: OBITUARIES: still nothing, under either Hovencamp or Mendoza. Her 2003 obituary remains unfound. NEWSPAPER ARCHIVES: THIRTEEN New Jersey Herald articles for Ruth Hovencamp, 1963 to 1999 - and newspapers.com, which holds that paper well, returns NOTHING for the surname in New Jersey. The two services genuinely do not index the same thing, which is the whole reason the standing rule demands both. The first opened is her WEDDING REPORT with a PHOTOGRAPH -> [J.568]: married 6 Sep 1970 at the parsonage of the Sussex First Baptist Church, her mother named as 'Mrs. Ella M. Ogden of RD 2, Sussex', the couple to live at 3 Fourth St., Sussex, and she lately elected Sussex County president of the American Legion Auxiliary. TWELVE REMAIN UNOPENED and are carried as a todo at [J.568]; the 12 Sep 1999 item is the one to open first.
genealogybank 2026-10-22 · Attempted: New Jersey obituaries, lname=Hovencamp fname=Ruth, aiming at her 2003 obituary.
Searched for: Attempted: New Jersey obituaries, lname=Hovencamp fname=Ruth, aiming at her 2003 obituary.
Result: SUPERSEDED THE SAME DAY - the maintainer logged in and the search was re-run; see the signed-in genealogybank row above. The original not-signed-in note is kept because it is the reason the re-run happened: had the unsubscribed 'did not match any items' been written down as a null, none of [J.568] to [J.579] would have been found. NOT RUN - NOT SIGNED IN. The page offered 'Login' and 'Get Started Now', i.e. this session has no GenealogyBank subscription, and no credentials were entered. The page did return 'Your search for Ruth Hovencamp did not match any items', and THAT IS NOT RECORDED AS A NULL: per the standing rule a GenealogyBank search counts only when run signed in, because an unsubscribed run searches a different and much smaller surface. The engine-search to-do for this person stays OPEN on GenealogyBank. It matters here specifically: newspapers.com has good New Jersey Herald coverage for 2003 and found nothing under Hovencamp, so GenealogyBank's different holdings are exactly the sort of place the obituary could still be.
newspapers com 2026-10-22 · HER 2003 OBITUARY, SIGNED IN (account avatar and My Clippings present). Three passes: keyword=Hovencamp&date-start=2003&date-end=2003...
Searched for: HER 2003 OBITUARY, SIGNED IN (account avatar and My Clippings present). Three passes: keyword=Hovencamp&date-start=2003&date-end=2003 nationally; a COVERAGE probe, keyword=Wantage for the same year, to find out whether New Jersey is held at all; and keyword=Mendoza for 2003.
Result: A REAL NULL ON HOVENCAMP, and the coverage probe is what makes it one. HOVENCAMP 2003: 69 matches nationally, broken down as Florida 36, New York 17, Kentucky 3, Maine 3, Alabama 2 - and NOT ONE IN NEW JERSEY. COVERAGE PROBE: Wantage in 2003 returns 7,596 matches of which 3,800+ are New Jersey, overwhelmingly the NEW JERSEY HERALD of Newton - the very paper that would have carried her obituary, well digitised for the right year. So the Hovencamp zero is an ABSENCE, not a coverage gap. Per [[reference_internet_archive_fulltext_search]] those are different states and only one of them tells you to look elsewhere. MENDOZA: not usable as a sweep - 88,422 matches for 2003. NOTE THE INSTRUMENT FAULT: the location=us-nj parameter was SILENTLY IGNORED, the result set being national (Florida 10K+, California 10K+, Texas 9K+). Same disease as the Ancestry residence parameter - a filter that ranks or is dropped rather than filtering. A Mendoza search here needs the location set through the form, not the URL. SO: she was not written up under HOVENCAMP in any New Jersey paper this service holds for 2003, and the MENDOZA question is still open.
google 2026-10-22 · Browser Google, second attempt at her 2003 obituary, this time under the name she was BURIED under rather than the one she died under:...
Searched for: Browser Google, second attempt at her 2003 obituary, this time under the name she was BURIED under rather than the one she died under: "Hovencamp" OR "Mendoza" Ruth obituary 2003 "New Jersey Herald" OR Beemerville OR Wantage.
Result: HER obituary: still NOT FOUND. But the first three results were all her HUSBAND'S ->
[J.567]: William (Bunky) D. Mendoza, b. Wilkes-Barre 6 May 1938, d. 17 Dec 2008, 'preceded in death by his wife, Ruth, who passed away in 2003', buried Beemerville Cemetery. That confirms the marriage from his side and gives him a full life - Korean War Navy radio operator, electrical line worker, I.B.E.W. - where an hour earlier
William D Mendoza had been a name on an index row. A LEAD ON THE DAUGHTER came from the same results page: a public comment thread about an unrelated Wantage death names a 'Diana Lynn Hovencamp'. That prompted a re-crop of the 1950 census cell, which now reads 'L Diana[?]' rather than the unresolved 'L[?]iana' - the same initial-first inversion the enumerator used for 'E Ruth'. See the reading note at
[D.870]: the corroboration prompted the look, it is not what the reading rests on.
state index 2026-10-22 · HER SECOND MARRIAGE. New Jersey marriage index coll. 61253, ?name=Ruth_Hovencamp - the surname [F.377] gave her from Mar 1946 - aimed at...
Searched for: HER SECOND MARRIAGE. New Jersey marriage index coll. 61253, ?name=Ruth_Hovencamp - the surname [F.377] gave her from Mar 1946 - aimed at the Sep 1970 change to Mendoza in that same record.
Result: FOUND, and it took one search -> [C.168]. Ruth E Hovencamp x WILLIAM D MENDOZA, Sep 1970, Sussex borough, Sussex Co., New Jersey, certificate 42402. Two rows returned; the other is an unrelated 1947 marriage to a Stephanos Mouroukis. The month matches [F.377] exactly. Note the contrast with her FIRST marriage: the 1970 form decodes a municipality, a month and a certificate number, where the 1945-48 form carries four names and nothing else ([C.165], [C.166]). Same index, same question, a morning against a minute.
findagrave 2026-10-22 · Find a Grave by name. FIRST under the name she died with - Mendoza, Ruth, d. 2003 +/- 5 years, New Jersey (the page echoed the filter...
Searched for: Find a Grave by name. FIRST under the name she died with - Mendoza, Ruth, d. 2003 +/- 5 years, New Jersey (the page echoed the filter back as 'New Jersey, USA', so the location bound). THEN under Hovencamp: ?firstname=Ruth&lastname=Hovencamp, no dates, no location.
Result: MENDOZA: NO MATCHES - a true null for the name she actually died under. HOVENCAMP: 2 records, and the second is HERS - 'Ruth E. Hovencamp, 1928-2003, Beemerville Cemetery, Beemerville, Sussex County, New Jersey', memorial 11428626 -> [G.684]. Parsed with scripts/fetch_findagrave.ps1, not transcribed. THE PANEL GAVE THE HUSBAND AND HIS DATES: PFC Herbert L. Hovencamp, 2 Nov 1925 - 23 Feb 1969, memorial 11428623 -> [G.685], with the inscription 'World War II N.J. PFC U.S. Army'. His death at 43 is what makes a Sep 1970 remarriage intelligible. SHE IS BURIED UNDER HER FIRST MARRIED NAME, which is why the Mendoza search was a null and why no earlier search could have reached her.
google 2026-10-22 · Browser Google, per the post-1995 death rule: "Ruth Mendoza" obituary 2003 Sussex New Jersey.
Searched for: Browser Google, per the post-1995 death rule: "Ruth Mendoza" obituary 2003 Sussex New Jersey.
Result: NULL. Two results, neither relevant - a Gulf of Mexico regulatory comment list and a Charlotte Ruth Mendoza Jones of Palo Cedro, California. Not retried under HOVENCAMP, which on the evidence of [G.684] may be the better name; that is in the obituary todo.
ancestry all 2026-10-22 · HER 1950 CENSUS under the surname CROWELL, which [F.377] shows she used from at least Jan 1944. Two passes on coll. 62308:...
Searched for: HER 1950 CENSUS under the surname CROWELL, which [F.377] shows she used from at least Jan 1944. Two passes on coll. 62308: ?name=Ruth_Crowell&birth=1928&birth_x=1-0-2&count=50, and then the surname-plus-residence recipe ?name=_Crowell&residence=_sussex-new+jersey-usa_2837&residence_x=1-0-0_1-0.
Result: BOTH NULL, and both bounded. The name search returns 47 rows, ALL READ, with no New Jersey Ruth Crowell in them - the engine fuzzes heavily into Correll, Coryell, Coriell, Croall and Carewell. The county recipe returns 21 rows, ALL READ, being every Crowell enumerated in Sussex Co. in 1950, and there is no Ruth among them. So she was not living under Crowell in her home county. WORTH KEEPING FOR
Ella M. (Crowell) Cooper: those 21 rows are Ella's own Crowell people in Wantage - Clarence L (b. abt 1888), Charles E (abt 1905) with wife Myrtle, William C (abt 1918), Merrill W and Irene M, Donald L and Betty E. Charles E is a candidate for the Charles Crowell, 35, boarding in the Ogden household in 1940
[D.868]. Noted at
Ella M. (Crowell) Cooper, not asserted.
ancestry all 2026-10-22 · HER 1950 CENSUS with NO SURNAME AT ALL, because by then she could be under any married name. Coll. 62308, given name only plus the...
Searched for: HER 1950 CENSUS with NO SURNAME AT ALL, because by then she could be under any married name. Coll. 62308, given name only plus the county: ?name=Ruth*_&birth=1928&birth_x=1-0-1&residence=_sussex-new+jersey-usa_2837&residence_x=1-0-0_1-0 - every woman called Ruth born about 1927-1929 enumerated in Sussex Co., New Jersey.
Result: 19 rows, ALL READ - and SHE IS IN THEM, as 'E Ruth Hovencan', wife of Herbert, Newton. Not recognised at the time, because no Ruth E. appears in the list and the surname meant nothing yet; it was [F.377] half an hour later that named Hovencamp and sent me back to this list. THE INSTRUMENT WORKED AND I ALMOST WASTED IT. Recorded because the lesson is reusable: a given-name-plus-county sweep will contain a married woman under a surname you have never heard of, so the list is only as good as the independent evidence you bring back to it.
ancestry all 2026-10-22 · THE SOCIAL SECURITY APPLICATIONS AND CLAIMS INDEX, re-opened. It had been cited on this file for its death date alone and its NOTES...
Searched for: THE SOCIAL SECURITY APPLICATIONS AND CLAIMS INDEX, re-opened. It had been cited on this file for its death date alone and its NOTES field had never been read. Reached by ?name=Ruth+Evelyn_Hovencamp on coll. 60901 once [C.167] suggested the surname; her record returns FIRST even though 'Hovencamp' is not in its indexed name, because it sits in the record's own alternate-name list.
Result: THE ANSWER, and it had been sitting in a record the catalog already cited -> [F.377]. The notes field is a DATED NAME HISTORY: 'Jan 1944: Ruth Evelyn Crowell; Mar 1946: Ruth E Hovencamp; Sep 1970: Ruth Eve Mendoza; 02 Apr 2003: Ruth E Mendoza', with father Harry Cooper, mother Ella M Crowell, b. 22 Feb 1928 Sussex, d. 25 Mar 2003. LESSON, and it is the one worth keeping from this whole morning: the file had quoted this record for ONE field. Every other field in it, including the one that answered the open question, had gone unread for as long as the question had been open.
state index 2026-10-22 · NEW JERSEY BRIDE MARRIAGE INDEX for a bride surnamed CROWELL. Coll. 61253, ?name=Ruth_Crowell&name_x=1_1, exact given and surname, no...
Searched for: NEW JERSEY BRIDE MARRIAGE INDEX for a bride surnamed CROWELL. Coll. 61253, ?name=Ruth_Crowell&name_x=1_1, exact given and surname, no date filter.
Result: ONE ROW IN THE WHOLE INDEX, 1901-2016: Ruth Crowell x Herbert L Hovencamp, 1946, 'New Jersey' ->
[C.167]. Against the Mar 1946 name change in
[F.377] and the Newton household in
[D.870], that single row is the marriage.
ancestry all 2026-10-22 · HER MARRIED SURNAME, sought in the New Jersey Marriage Index 1901-2016 (Ancestry coll. 61253) - the instrument that produced [C.160] to...
Searched for: HER MARRIED SURNAME, sought in the New Jersey Marriage Index 1901-2016 (Ancestry coll. 61253) - the instrument that produced
[C.160] to
[C.164] on 2026-10-19.
?name=Ruth_Cooper&name_x=1_1&count=50 - exact given AND surname, no date filter so the whole run of the index is in view:
57 rows, BOTH PAGES READ. The window that matters is about 1945 to April 1950, because
[D.869] shows she had left her mother's household by census day at 22.
Result: NOT A NULL, AND NOT AN ANSWER - the index cannot discriminate in the window that matters, and that is the finding. NO Ruth Cooper marriage anywhere in this index is placed in SUSSEX COUNTY, 1901-2016. But the rows before about 1949 CARRY NO COUNTY AT ALL: their place column reads simply 'New Jersey'. Six such rows fall in the window - 1945 Joseph S Gray, 1945 Ronald H MacPherson, 1946 Thomas J Golden, 1946 William C Lindengrass, 1947 John D Geils, 1948 Joseph R Sanders - and any one of them could be her. None is indicated. THE DATED-PLACE ROWS IN THE WINDOW ARE ALL WRONG COUNTIES: Mar 1949 Newark (Jenni Berry), Mar 1949 Kearny, Hudson (Collin Weir), Jul 1949 Elizabeth, Union (Willi Black). The Kearny row is the only 'Ruth E Cooper' before census day and is NOT adopted: Kearny is fifty miles from Wantage and nothing but the initial connects them. The two later Ruth E Coopers, Nov and Dec 1950, are after census day and so cannot explain her absence from the household. WHAT WOULD DISCRIMINATE: the index images themselves for the 1945-48 volumes, which carry a place CODE even where the Ancestry index does not decode it - exactly the situation [C.161] to [C.164] were read out of. That is the next move and it is a reading task, not a search. CORRECTION, SAME DAY: the closing sentence above was wrong and is retained so the change is visible. It said the 1945-48 index IMAGES 'carry a place CODE even where the Ancestry index does not decode it', reasoning from [C.161]-[C.164], which are 1950, 1965, 1975 and 1977. That was an inference from later volumes, not a reading of these ones. The 1945 and 1948 pages were then pulled and read ([C.165], [C.166]) and the form for those years has NO place column at all - four names and nothing else. Ancestry's bare 'New Jersey' is faithful to the document. The route is CLOSED, not merely unworked.
state index 2026-10-22 · THE INDEX IMAGES THEMSELVES, to test whether the 1945-48 bride-index form carries the numeric place code that the 1950+ volumes carry....
Searched for: THE INDEX IMAGES THEMSELVES, to test whether the 1945-48 bride-index form carries the numeric place code that the 1950+ volumes carry. Browsed coll. 61253 - Browse this collection, Index Type 'Bride Index', Year Range '1945' then '1948', Surname Range 'A - Z' / 'A - K' - and interpolated to the COOPER block in each: 1945 image 106 of 629 (b428678), 1948 image 141 of 406 (b428683). Both downloaded and read on zoom.py crops.
Result: THE ROUTE IS CLOSED, and the negative is about the FORM. Both years carry exactly four labelled columns - wife's surname before marriage, her Christian name, husband's surname, his Christian name - and the two unlabelled columns to their right are EMPTY, read at 2x on both pages. No county, no month, no certificate number. The 'B-I BINDING' lettering on the right of the 1945 sheet is a filming target, not a column head. 1945 and 1948 bracket the whole candidate window, so the three unread 1946-47 rows were deliberately not pulled - the form cannot discriminate, so their images could only reproduce Ancestry's index. Entries [C.165] and [C.166]; the candidate set is listed in [name.217]. ALSO LEARNED, and worth more than this search was: on coll. 61253 the marriage_x=1-0-N range token is IGNORED and the real window is plus or minus ONE year. Probed three ways. A date-filtered sweep of this collection that trusted the token would return a confident false null.
ancestry all 2026-10-22 · HER 1950 CENSUS, approached through the household she was in ten years earlier. Ancestry coll. 62308:...
Searched for: HER 1950 CENSUS, approached through the household she was in ten years earlier. Ancestry coll. 62308: ?name=Reed_Ogden&birth=1907&birth_x=1-0-0 returns 26 rows with no New Jersey Ogden (the engine fuzzes Reed into Ruth and R-initials) and ZERO with name_x=1_1; the surname-only recipe bounded to the county, ?name=_Ogden&residence=_sussex-new+jersey-usa_2837&residence_x=1-0-0_1-0, returns 11 rows and finds the household at once.
Result: FOUND the household ->
[D.869], and SHE IS NOT IN IT. Reed R 41, Ella M 42, Reed R Jr 20, Elsie M 16, Marion E 13 and a fourth daughter Joan N 9 - no Ruth. She was 22. So her 1950 gap is now BOUNDED rather than closed: she had left her mother's house by April 1950 and must be sought under a married name, or as a lodger or live-in worker. That is worth more than another null on her own name, which is what a search for 'Ruth Cooper' would have produced.
ancestry all 2026-10-22 · HER 1940 CENSUS, and it was NOT searched on her own name. Her mother Ella M. (Crowell) Cooper remarried REED R. OGDEN in 1930 [C.160],...
Searched for: HER 1940 CENSUS, and it was NOT searched on her own name. Her mother
Ella M. (Crowell) Cooper remarried REED R. OGDEN in 1930
[C.160], so at twelve she would be in her stepfather's household under his surname. Ancestry coll. 2442,
?name=Reed_Ogden&birth=1907&birth_x=1-0-0&count=50 - 17 rows, ALL READ; the household is row 1.
Result: FOUND ->
[D.868]: Wantage Twp, Sussex Co., household 7, where she appears as 'Ruth', daughter, 12, under the Ogden surname ditto. THE SURNAME COOPER IS NOT ON THE SHEET, so no search on her own name could ever have reached her - the 'no search recorded' on the worklist was concealing a gap that was unworkable from her side. The route in was the stepfather's name, which the catalog has only held since
[C.160] was found on 2026-10-19, three days before this search. The plate also gives two half-sisters the catalog did not have, Elsie (6) and Marion (2), and a Charles Crowell, 35, boarding.
google 2026-10-13 · Google (browser): "Ruth E. Cooper" OR "Ruth Evelyn Cooper" obituary 2003 New Jersey.
Searched for: Google (browser): "Ruth E. Cooper" OR "Ruth Evelyn Cooper" obituary 2003 New Jersey.
Result: NULL - other Ruth E. Coopers (Lyonsdale NY 2006, Port Richey FL 2019, Augusta GA May 2003 - born Kearny NJ, a retired restaurant owner; not opened, and the date (25 May) is not hers (25 Mar 2003)).
genealogybank 2026-10-04 · SIGNED IN. New Jersey obituaries, Ruth Cooper, 1 Jan - 31 Dec 2003.
Searched for: SIGNED IN. New Jersey obituaries, Ruth Cooper, 1 Jan - 31 Dec 2003.
Result: NULL: no obituary matches (the database showed 8 newspaper-archive hits, not opened).
findagrave 2026-10-04 · Not re-run; her stone is on [G.218].
Searched for: Not re-run; her stone is on [G.218].
Result: Not run.
newspapers com 2026-10-04 · Not run - year-only death date and possibly a married surname; GenealogyBank run instead.
Searched for: Not run - year-only death date and possibly a married surname; GenealogyBank run instead.
Result: Not run.
familysearch tree 2026-10-13 · FamilySearch tree: Ruth Cooper, b. 1927-1929, d. 2003, birthplace New Jersey.
Searched for: FamilySearch tree: Ruth Cooper, b. 1927-1929, d. 2003, birthplace New Jersey.
Result: NULL on the first page - Ruth Helen Cooper (1928-2013, Palmyra NJ, parents William Cooper Sr and Emma Alice Roach) and Ruth Carr Cooper (1923-2003, Summit NJ, parents William Mifflin Cooper and Edith Hendrickson Kingdon), neither this Ruth.
ancestry all 2026-10-04 · Not run this pass.
Searched for: Not run this pass.
Result: Not run.
familysearch records 2026-10-05 · Ruth Cooper, b. 1926-1930, father's given name Harry (49,775; first 100 read); Ruth Cooper, b. 1926-1930, mother's given name Ella, any...
Searched for: Ruth Cooper, b. 1926-1930, father's given name Harry (49,775; first 100 read); Ruth Cooper, b. 1926-1930, mother's given name Ella, any place NJ (4,438; census rows read); Harry Cooper, b. 1905-1908, residence Sussex Co. NJ (17,368; first 12).
Result: FOUND: Sussex birth index 22 Feb 1928, vol. 14 p. 184, under both Cooper and Crowell
[F.328]. NULL: Harry's 1930 and 1940 households not found in the index under Sussex (1910 and 1920 are his parents' households; 1950
[D.356] he is alone); Ruth's 1930/1940/1950 not identified - a 1950 'Ruth Cooper', b. 1929 N.J., wife of Robert A., Mount Arlington, Morris Co. (1:1:6F9Y-HCTL) is not her unless she married a Cooper; no marriage, death or land record found (married name unknown).
ancestry all 2026-10-06 · Ancestry 'U.S., Social Security Applications and Claims Index, 1936-2007' (coll. 60901): Ruth E Cooper, birth 1928 +/-1 (name search; up...
Searched for: Ancestry 'U.S., Social Security Applications and Claims Index, 1936-2007' (coll. 60901): Ruth E Cooper, birth 1928 +/-1 (name search; up to 12 candidate records opened and filtered on given name and birth year).
Result: FOUND (record 47978586): 'Ruth Evelyn Crowell', b. 22 Feb 1928, Sussex Susse[x], New Jersey; d. 25 Mar 2003; father Harry Cooper; mother Ella M Crowell. Gives her middle name (Evelyn), her death day, and both parents by name.